@jsenv/dom 0.17.37 → 0.17.40

package/dist/jsenv_dom.js

@@ -7522,17 +7522,50 @@ const getScrollbarState = (
  * @param {Element} [options.container] - The scroll container to scroll. Defaults to getScrollContainer(el).
  * @param {"start"|"center"|"end"|"nearest"} [options.block="nearest"] - Vertical alignment.
  * @param {"start"|"center"|"end"|"nearest"} [options.inline="nearest"] - Horizontal alignment.
+ * @param {"auto"|"instant"|"smooth"} [options.behavior] - Left out, the container's CSS scroll-behavior decides; "instant" is for a caller that measures the result in the same tick.
  */
 const scrollIntoViewScoped = (
   el,
-  { container = getScrollContainer(el), ...rest } = {},
+  { container = getScrollContainer(el), behavior, ...rest } = {},
 ) => {
   if (!container) {
     return;
   }
-  container.scrollTo(
-    getScrollIntoViewScopedOffsets(el, { container, ...rest }),
-  );
+  container.scrollTo({
+    behavior,
+    ...getScrollIntoViewScopedOffsets(el, { container, ...rest }),
+  });
+};
+
+/**
+ * Scrolls `el` into view in every scroll container between it and the
+ * document, innermost first — the chain `Element.prototype.scrollIntoView`
+ * walks, minus the boxes nobody can scroll back.
+ *
+ * `overflow: hidden` is the one that matters: it IS a scroll container, so
+ * the native call spends scroll on it as readily as on any other, and there
+ * it is spent for good — no scrollbar, no wheel, no touch gives it back. A
+ * card clipping a drawing, holding something that overlaps its edge by 2px,
+ * ends up 2px off until it re-renders. Only the containers `isScrollable`
+ * recognizes on its own (without `includeHidden`) are moved; the ones that
+ * merely clip are left where they are.
+ *
+ * Each container measures `el` where the inner ones just put it, so the outer
+ * ones see the final position rather than the one they started from.
+ *
+ * @param {Element} el - The element to scroll into view.
+ * @param {object} options - the same as scrollIntoViewScoped's, minus container.
+ */
+const scrollIntoViewThroughScrollables = (el, options) => {
+  for (const scrollContainer of getScrollContainerSet(el)) {
+    // getScrollContainerSet already skips what only clips, except at the end
+    // of the chain: with nothing scrollable left to find it hands back the
+    // document scroller, which a scroll lock may have turned into a clip too.
+    if (!isScrollable(scrollContainer)) {
+      continue;
+    }
+    scrollIntoViewScoped(el, { ...options, container: scrollContainer });
+  }
 };
 
 /**
@@ -7554,7 +7587,6 @@ const getScrollIntoViewScopedOffsets = (
     inline = "nearest",
   } = {},
 ) => {
-  const containerRect = container.getBoundingClientRect();
   const elRect = el.getBoundingClientRect();
   const style = getComputedStyle(el);
 
@@ -7565,15 +7597,35 @@ const getScrollIntoViewScopedOffsets = (
 
   const currentScrollTop = container.scrollTop;
   const currentScrollLeft = container.scrollLeft;
-  const containerHeight = containerRect.height;
-  const containerWidth = containerRect.width;
+
+  // Where the container shows its content, in the coordinates
+  // getBoundingClientRect speaks. The document scroller is a case apart: what
+  // it shows is the viewport, sitting at the origin of those coordinates,
+  // while its own box is the whole page and travels with the scroll — reading
+  // that box would count the scroll twice and compare the element to the
+  // height of the document rather than the height of the screen.
+  let containerTop;
+  let containerLeft;
+  let containerHeight;
+  let containerWidth;
+  if (container === container.ownerDocument.scrollingElement) {
+    containerTop = 0;
+    containerLeft = 0;
+    containerHeight = container.clientHeight;
+    containerWidth = container.clientWidth;
+  } else {
+    const containerRect = container.getBoundingClientRect();
+    containerTop = containerRect.top;
+    containerLeft = containerRect.left;
+    containerHeight = containerRect.height;
+    containerWidth = containerRect.width;
+  }
 
   // Element position relative to the container's scroll origin.
-  const elTop =
-    elRect.top - containerRect.top + currentScrollTop - scrollMarginTop;
+  const elTop = elRect.top - containerTop + currentScrollTop - scrollMarginTop;
   const elBottom = elTop + elRect.height + scrollMarginTop + scrollMarginBottom;
   const elLeft =
-    elRect.left - containerRect.left + currentScrollLeft - scrollMarginLeft;
+    elRect.left - containerLeft + currentScrollLeft - scrollMarginLeft;
   const elRight = elLeft + elRect.width + scrollMarginLeft + scrollMarginRight;
 
   let newScrollTop = currentScrollTop;
@@ -9455,6 +9507,14 @@ installImportMetaCssBuild(import.meta);/**
  * A tap is left alone by that: a press that goes nowhere is still a press, which
  * is what a piece that is also a link or a card needs.
  *
+ * A HOLD is not, and nothing in such a place is text to select. Taking the wait
+ * away takes away the only thing that answered a finger held still, so the
+ * browser answers it alone: its own long press selects the word under the thumb,
+ * and the card the hand meant to carry is left blue and handled. Said to every
+ * pointer — a mouse there drags from the first few pixels, so a selection begun
+ * there is one that could never be finished either. What says its press is its
+ * own keeps its text (see the stylesheet below).
+ *
  * It is opt-in and cannot be anything else. Nothing here can see whether the
  * surroundings scroll — a page scrolls by default, an overflow is one CSS
  * property away, and getting it wrong the wrong way means the list runs away
@@ -9499,6 +9559,11 @@ const css$4 = /* css */`[data-drag-handle], [data-drag-source] {
 
 [data-drag-on-contact] [data-drag-source], [data-drag-source][data-drag-on-contact] {
   touch-action: pinch-zoom;
+  user-select: none;
+}
+
+[data-drag-on-contact] [data-drag-ignore], [data-drag-on-contact] [popover], [data-drag-on-contact] dialog, [data-drag-on-contact] :is(input:not([data-press-only]), textarea), [data-drag-on-contact] :is([contenteditable=""], [contenteditable="true"]) {
+  user-select: text;
 }
 
 [data-drag-ignore], [data-self-interactions~="drag"], [data-self-interactions~="*"], [data-drag-source] [popover], [data-drag-source] dialog {
@@ -13420,27 +13485,78 @@ const DRAG_FLICK_DISTANCE = 8;
 // way. Let go and it comes back — a wall one can lean on, never walk through.
 const DRAG_RESISTANCE = 0.3;
 
-// What a drag must not start on: something that reads the pointer itself, whole,
-// with no axis left to share. A button or a link is not in the list — dragging
-// from one travels, and the click it would have made is swallowed on the way
-// out. A drag SOURCE is not either: it says which way it goes and only takes
-// that (see DRAG_SOURCE_AXES_ATTRIBUTE) — but a dedicated handle is, being a
-// place whose only purpose is to be taken hold of, from the first pixel. And so
-// is an element naming `drag` among its own interactions: it said the grab is
-// ITS, here, rather than the box's — and one that named only the click said
-// nothing to this gesture and is passed through (see DRAG_IGNORED_SELECTOR in
-// drag_to.js). And so is a popover or a dialog: a layer OVER the box, whose
-// press only bubbles through the box because the layer is anchored in it.
-const DRAG_EXCLUDED_SELECTOR = [
-// The fields that read the pointer as it MOVES: a caret dragged through text,
-// a thumb pushed along its rail, a spinner. The ones that only read the
-// press — a checkbox, a radio, a colour, a file — are buttons by another
-// name, and like a button they let the drag through, the click they would
-// have made swallowed on the way out. Which matters more than the list makes
-// it look: a selectable row is covered by an invisible radio of its own, so
-// excluding every input at once means a list of rows inside a travelling box
-// that no finger can push.
-'input:not([type="checkbox"], [type="radio"], [type="button"], [type="submit"], [type="reset"], [type="image"], [type="color"], [type="file"])', "textarea", "select", '[contenteditable=""]', '[contenteditable="true"]', "[data-drag-handle]", "[data-no-drag-travel]", '[data-self-interactions~="drag"]', '[data-self-interactions~="*"]', "[popover]", "dialog"].join(",");
+// The gestures a browser ALREADY answers where a pointer goes down, named here
+// rather than guessed at from a tag: what is native is the whole reason a travel
+// must not start there. A caret dragged through text, a thumb pushed along its
+// rail, a menu fed by everything that follows the press — taking the press from
+// one of those takes away something the element cannot offer a second time, and
+// a travel is never worth that.
+//
+// What is NOT in the list has nothing to lose. A button or a link is out on
+// purpose: dragging from one travels, and the click it would have made is
+// swallowed on the way out. So are the inputs that read the press and nothing
+// after it (a checkbox, a radio, a colour, a file) — buttons by another name.
+// Which matters more than it looks: a selectable row is covered by an invisible
+// radio of its own, so excluding every input at once means a list of rows inside
+// a travelling box that no finger can push.
+//
+// Every entry answers "never", and the entry is where a softer answer would be
+// written if one turned out to be worth it — per hand, since that is where these
+// gestures differ. The one that comes to mind is a travel a MOUSE could still
+// ask for by holding still first, a hold meaning nothing to a mouse in a text
+// field: it is not here because the browser has already begun a selection at the
+// press, and nothing hands that back mid-gesture — the travel would drag a
+// selection along with it. With a finger the hold is the selection UI itself, so
+// there is nothing to take there either.
+const PRESSED_INPUT_TYPES = ['[type="checkbox"]', '[type="radio"]', '[type="button"]', '[type="submit"]', '[type="reset"]', '[type="image"]', '[type="color"]', '[type="file"]'].join(",");
+const NATIVE_POINTER_GESTURES = [{
+  // The value follows the pointer, pixel by pixel: a thumb along its rail, a
+  // spinner clicked up and down. There is no moment in that which could be
+  // given away — the gesture IS the pointer.
+  selector: 'input[type="range"],input[type="number"]'
+}, {
+  // The text answers the pointer, and differently per hand: a mouse drags a
+  // caret through it (a selection), a finger drags the field's own content
+  // sideways when it overflows, and a finger held still opens the selection
+  // UI. Three things a field is for, against one travel that has a whole box
+  // to start from.
+  selector: [`input:not(${PRESSED_INPUT_TYPES},[type="range"],[type="number"])`, "textarea", '[contenteditable=""]', '[contenteditable="true"]'].join(",")
+}, {
+  // A menu opens under the pointer and the browser keeps the rest of the
+  // gesture: dragged over, it picks an option.
+  selector: "select"
+}];
+
+// …and what an element says against its own tag. Every line above is about what
+// an element DOES, and a tag only says what it IS: a picker's façade is an
+// <input> that opens a popup on the press and reads nothing at all as the
+// pointer moves (it selects its own text on mousedown, and that is the whole of
+// it). Only the element knows that, so only the element can say it — and having
+// said it, it is a button by another name like the others, and a travel starts
+// there like anywhere else.
+//
+// Said rather than found, and said on the element the pointer lands on: a
+// promise about a gesture has to be readable before the gesture exists, from
+// nothing but the DOM under the finger. And it is a promise: an element that
+// says it while the browser still answers the pointer there (a range, a field
+// that can really be typed in) has not made a travel possible, it has taken the
+// gesture the user was making away from them.
+const PRESS_ONLY_ATTRIBUTE = "data-press-only";
+const NATIVE_POINTER_GESTURE_SELECTOR = NATIVE_POINTER_GESTURES.map(({
+  selector
+}) => `:is(${selector}):not([${PRESS_ONLY_ATTRIBUTE}])`).join(",");
+
+// What a drag must not start on: what answers the pointer natively (above),
+// plus what has said the gesture is its own. A drag SOURCE is not in the list:
+// it says which way it goes and only takes that (see DRAG_SOURCE_AXES_ATTRIBUTE)
+// — but a dedicated handle is, being a place whose only purpose is to be taken
+// hold of, from the first pixel. And so is an element naming `drag` among its
+// own interactions: it said the grab is ITS, here, rather than the box's — and
+// one that named only the click said nothing to this gesture and is passed
+// through (see DRAG_IGNORED_SELECTOR in drag_to.js). And so is a popover or a
+// dialog: a layer OVER the box, whose press only bubbles through the box because
+// the layer is anchored in it.
+const DRAG_EXCLUDED_SELECTOR = [NATIVE_POINTER_GESTURE_SELECTOR, "[data-drag-handle]", "[data-no-drag-travel]", '[data-self-interactions~="drag"]', '[data-self-interactions~="*"]', "[popover]", "dialog"].join(",");
 
 // Which axes a box travels on, one attribute per gesture, said in the DOM by
 // whoever owns the box: it is what a box ABOVE another reads to know the
@@ -14226,6 +14342,42 @@ const isPressExcluded = (target, element) => {
   return Boolean(excluded) && !excluded.contains(element);
 };
 
+/**
+ * Whether a press landing on `element` may become the gesture of something
+ * around it — a box that travels by drag, an object carried out of a list. Or
+ * of the element itself, when the element is that box: the gesture is still one
+ * the press is being asked for.
+ *
+ * The question a control that acts ON THE PRESS has to ask before it acts: a
+ * picker opening its popup at the pointerdown, the way a native select does,
+ * is right only while nothing else disputes that press. Where a box above
+ * travels, the finger going down is the beginning of something that is not yet
+ * a choice — answering there both answers for a user who has chosen nothing and
+ * takes the press from a gesture that could then never form. What such a control
+ * does instead is wait for the click, which the browser only delivers if the
+ * press stayed a press: a gesture swallows the one it leaves behind.
+ *
+ * Asked of the DOM at the press rather than worked out at render, because that
+ * is where the answer lives: the box above says what it travels by
+ * (DRAG_AXES_ATTRIBUTE, DRAG_SOURCE_AXES_ATTRIBUTE), and whether the press is
+ * takeable at all is the same question the gesture itself asks a moment later —
+ * a field the travel would never have started on disputes nothing, and a control
+ * inside one goes on acting on the press.
+ *
+ * @param {Element} element Where the press landed.
+ * @returns {boolean}
+ */
+const isPressDisputedByDrag = element => {
+  if (!element || typeof element.closest !== "function") {
+    return false;
+  }
+  const dragged = element.closest(`[${DRAG_AXES_ATTRIBUTE}],[${DRAG_SOURCE_AXES_ATTRIBUTE}]`);
+  if (!dragged) {
+    return false;
+  }
+  return !isPressExcluded(element, dragged);
+};
+
 // Shared by navi's own use_displayed_layout_effect.js (rich "navi_displayed"
 // CustomEvent, open transitions only) and visible_rect.js (needs both
 // directions: hide when a container closes, recheck when it reopens) — the
@@ -20087,4 +20239,4 @@ const useResizeStatus = (elementRef, { as = "number" } = {}) => {
   };
 };
 
-export { EASING, ELEMENT_SIZE_CHANGE, activeElementSignal, addActiveElementEffect, addAttributeEffect, allowWheelThrough, appendStyles, applyNewPosition, canScroll, captureScrollState, chainEvent, claimWheelGesture, clickIsSuppressed, closestOpenableAncestor, contrastColor, createBackgroundColorTransition, createBackgroundTransition, createBorderRadiusTransition, createBorderTransition, createDragGestureController, createDragToMoveGestureController, createEventGroupLogger, createGroupTransitionController, createHeightTransition, createIterableWeakSet, createOpacityTransition, createPubSub, createStyleController, createTimelineTransition, createTransition, createTranslateXTransition, createValueEffect, createWidthTransition, cubicBezier, dispatchCustomEvent, dispatchInternalCustomEvent, dispatchPublicCustomEvent, dragAfterIntent, elementIsFocusable, elementIsVisibleForFocus, elementIsVisuallyVisible, findAfter, findAncestor, findBefore, findDescendant, findEvent, findFocusDelegateTarget, findFocusable, findSelfOrAncestorFixedPosition, formatEventSideEffect, getAncestorOpenType, getAvailableHeight, getAvailableWidth, getBackground, getBackgroundColor, getBorder, getBorderRadius, getBorderSizes, getContrastRatio, getDefaultStyles, getDragCoordinates, getDropTargetInfo, getElementSignature, getFirstVisuallyVisibleAncestor, getFocusVisibilityInfo, getHeight, getHeightWithoutTransition, getInnerHeight, getInnerWidth, getKeyboardEventDefaultAction, getLuminance, getMarginSizes, getMaxHeight, getMaxWidth, getMinHeight, getMinWidth, getOpacity, getOpacityWithoutTransition, getPaddingSizes, getPositionedParent, getPositioningScrollOffset, getPreferedColorScheme, getScrollBox, getScrollContainer, getScrollContainerSet, getScrollIntoViewScopedOffsets, getScrollRelativeRect, getSelfAndAncestorScrolls, getStyle, getTranslateX, getTranslateXWithoutTransition, getTranslateY, getVirtualKeyboardOverlayHeight, getVisuallyVisibleInfo, getWidth, getWidthWithoutTransition, hasCSSSizeUnit, initFlexDetailsSet, initFocusGroup, initPositionSticky, isAncestorOpen, isDisplayedDespiteClosedAncestor, isPrimaryButtonEvent, isSameColor, isScrollable, isTouchDrivenEvent, markDragSource, measureLongestVisualLineWidth, measureScrollbar, measureWidestChildRow, mergeOneStyle, mergeTwoStyles, normalizeKeyboardKey, normalizeStyle, normalizeStyles, observeAncestorOpenState, onAncestorReopen, parsePositionArea, parseStyle, performTabNavigation, pickPositionRelativeTo, prefersDarkColors, prefersLightColors, preventFocusNav, preventFocusNavViaKeyboard, preventIntermediateScrollbar, releaseWheelGesture, resolveCSSColor, resolveCSSSize, resolveColorLuminance, resolveOklchLightness, scrollIntoViewScoped, scrollIntoViewWithStickyAwareness, scrollRoomTowards, setAttribute, setAttributes, setStyles, setVirtualKeyboardOverlaysContent, snapToPixel, startDragTo, startDragToResizeGesture, startDragToTravel, stickyAsRelativeCoords, stringifyStyle, subscribeVirtualKeyboardGeometryChange, subscribeVisualViewportResizeSettled, subscribeWindowResizeSettled, suppressClickAfterGesture, trapFocusInside, trapScrollInside, useActiveElement, useAvailableHeight, useAvailableWidth, useMaxHeight, useMaxWidth, useResizeStatus, visibleRectEffect, waitForPressHeld, watchWheelTravel, wheelGestureIsTakenFrom };
+export { EASING, ELEMENT_SIZE_CHANGE, activeElementSignal, addActiveElementEffect, addAttributeEffect, allowWheelThrough, appendStyles, applyNewPosition, canScroll, captureScrollState, chainEvent, claimWheelGesture, clickIsSuppressed, closestOpenableAncestor, contrastColor, createBackgroundColorTransition, createBackgroundTransition, createBorderRadiusTransition, createBorderTransition, createDragGestureController, createDragToMoveGestureController, createEventGroupLogger, createGroupTransitionController, createHeightTransition, createIterableWeakSet, createOpacityTransition, createPubSub, createStyleController, createTimelineTransition, createTransition, createTranslateXTransition, createValueEffect, createWidthTransition, cubicBezier, dispatchCustomEvent, dispatchInternalCustomEvent, dispatchPublicCustomEvent, dragAfterIntent, elementIsFocusable, elementIsVisibleForFocus, elementIsVisuallyVisible, findAfter, findAncestor, findBefore, findDescendant, findEvent, findFocusDelegateTarget, findFocusable, findSelfOrAncestorFixedPosition, formatEventSideEffect, getAncestorOpenType, getAvailableHeight, getAvailableWidth, getBackground, getBackgroundColor, getBorder, getBorderRadius, getBorderSizes, getContrastRatio, getDefaultStyles, getDragCoordinates, getDropTargetInfo, getElementSignature, getFirstVisuallyVisibleAncestor, getFocusVisibilityInfo, getHeight, getHeightWithoutTransition, getInnerHeight, getInnerWidth, getKeyboardEventDefaultAction, getLuminance, getMarginSizes, getMaxHeight, getMaxWidth, getMinHeight, getMinWidth, getOpacity, getOpacityWithoutTransition, getPaddingSizes, getPositionedParent, getPositioningScrollOffset, getPreferedColorScheme, getScrollBox, getScrollContainer, getScrollContainerSet, getScrollIntoViewScopedOffsets, getScrollRelativeRect, getSelfAndAncestorScrolls, getStyle, getTranslateX, getTranslateXWithoutTransition, getTranslateY, getVirtualKeyboardOverlayHeight, getVisuallyVisibleInfo, getWidth, getWidthWithoutTransition, hasCSSSizeUnit, initFlexDetailsSet, initFocusGroup, initPositionSticky, isAncestorOpen, isDisplayedDespiteClosedAncestor, isPressDisputedByDrag, isPrimaryButtonEvent, isSameColor, isScrollable, isTouchDrivenEvent, markDragSource, measureLongestVisualLineWidth, measureScrollbar, measureWidestChildRow, mergeOneStyle, mergeTwoStyles, normalizeKeyboardKey, normalizeStyle, normalizeStyles, observeAncestorOpenState, onAncestorReopen, parsePositionArea, parseStyle, performTabNavigation, pickPositionRelativeTo, prefersDarkColors, prefersLightColors, preventFocusNav, preventFocusNavViaKeyboard, preventIntermediateScrollbar, releaseWheelGesture, resolveCSSColor, resolveCSSSize, resolveColorLuminance, resolveOklchLightness, scrollIntoViewScoped, scrollIntoViewThroughScrollables, scrollIntoViewWithStickyAwareness, scrollRoomTowards, setAttribute, setAttributes, setStyles, setVirtualKeyboardOverlaysContent, snapToPixel, startDragTo, startDragToResizeGesture, startDragToTravel, stickyAsRelativeCoords, stringifyStyle, subscribeVirtualKeyboardGeometryChange, subscribeVisualViewportResizeSettled, subscribeWindowResizeSettled, suppressClickAfterGesture, trapFocusInside, trapScrollInside, useActiveElement, useAvailableHeight, useAvailableWidth, useMaxHeight, useMaxWidth, useResizeStatus, visibleRectEffect, waitForPressHeld, watchWheelTravel, wheelGestureIsTakenFrom };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/dom",
-  "version": "0.17.37",
+  "version": "0.17.40",
   "type": "module",
   "description": "DOM utilities for writing frontend code",
   "repository": {