@signal9/era-ui 4.10.1 → 4.10.2

package/dist/ui/pane/pane-tab-list.svelte

@@ -8,23 +8,57 @@
 	// When the pane is too narrow to fit every tab, the strip scrolls (min-w-0 +
 	// overflow-x-auto — chromeless via scrollbar-none). The strip stays IN the
 	// pane's drag zone (no data-pane-control) so grabbing a tab drags the pane;
-	// overflow is scrolled by the mouse wheel (below) or native touch panning
-	// (touch-pan-x), not by a pointer drag — a drag moves the pane instead.
+	// overflow is scrolled by a horizontal gesture, the mouse wheel (below), or
+	// native touch panning (touch-pan-x), never by a pointer drag — a drag moves
+	// the pane instead.
 	//
+	// WHAT THIS HANDLER IS FOR, AND WHAT IT DELIBERATELY IS NOT
+	//
+	// A trackpad needs no help at all: a horizontally-overflowing container is
+	// scrolled by a two-finger left/right swipe natively, by the browser, with no
+	// JavaScript in the path — so the smoothest possible version of that gesture is
+	// the one we don't touch. Every `deltaX` returns early below for that reason.
+	//
+	// The handler exists for the ONE device that cannot express the gesture: a
+	// mouse, which has a single vertical axis. For that device — and only that
+	// device — a vertical notch is translated into horizontal scroll.
+	//
+	// The distinction is drawn from what the event itself reports, not from a
+	// user-agent guess:
+	//   • Firefox reports a mouse wheel in LINES (deltaMode 1); a trackpad always
+	//     reports pixels (deltaMode 0).
+	//   • Chromium and WebKit expose the legacy wheelDeltaY, which is exactly ±120
+	//     for one mouse notch. A trackpad's is derived from its pixel delta and
+	//     lands on that value only by coincidence.
+	//   • Shift is the conventional "scroll horizontally" modifier and works on any
+	//     device, so it is honoured whatever the deltas look like.
+	//
+	// A vertical trackpad swipe therefore does nothing here and falls through to
+	// the page, which is the point: the tabs are a horizontal strip, and scrolling
+	// them with a vertical flick was reading movement the user did not aim at them.
+	//
+	// KNOWN LIMIT: a high-resolution wheel (or Chromium's percent-based scrolling)
+	// emits fine-grained pixel deltas that look exactly like a trackpad's, so those
+	// wheels lose the vertical shortcut and scroll the strip with shift or a tilt
+	// wheel instead. That is the safe side to fail on — the opposite failure is the
+	// one being fixed.
+	const isMouseNotch = (e: WheelEvent) =>
+		e.deltaMode !== 0 ||
+		Math.abs((e as WheelEvent & { wheelDeltaY?: number }).wheelDeltaY ?? 0) === 120;
+
 	// The wheel listener needs non-passive registration (it calls preventDefault),
-	// so it's added imperatively rather than as an element prop: it translates a
-	// vertical mouse wheel into horizontal scroll while hovering the strip, and
-	// keeps the wheel captured even at an end so the page never takes over until
-	// the cursor leaves.
+	// so it's added imperatively rather than as an element prop.
 	$effect(() => {
 		const node = ref;
 		if (!node) return;
 		const onWheel = (e: WheelEvent) => {
 			const max = node.scrollWidth - node.clientWidth;
 			if (max <= 0) return; // no overflow — let the page scroll
-			const delta = Math.abs(e.deltaY) >= Math.abs(e.deltaX) ? e.deltaY : e.deltaX;
-			if (delta === 0) return;
-			node.scrollLeft = Math.max(0, Math.min(max, node.scrollLeft + delta));
+			// A horizontal delta is already the browser's job; never intercept it.
+			if (e.deltaX !== 0) return;
+			if (!e.shiftKey && !isMouseNotch(e)) return; // a trackpad's vertical swipe
+			if (e.deltaY === 0) return;
+			node.scrollLeft = Math.max(0, Math.min(max, node.scrollLeft + e.deltaY));
 			e.preventDefault();
 		};
 		node.addEventListener('wheel', onWheel, { passive: false });

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@signal9/era-ui",
-	"version": "4.10.1",
+	"version": "4.10.2",
 	"scripts": {
 		"dev": "vite dev --host",
 		"build": "vite build && npm run prepack",