@mintplayer/ng-bootstrap 21.24.0 → 21.25.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@mintplayer/ng-bootstrap",
   "private": false,
-  "version": "21.24.0",
+  "version": "21.25.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/MintPlayer/mintplayer-ng-bootstrap",

package/types/mintplayer-ng-bootstrap-dock.d.ts

@@ -84,6 +84,9 @@ declare class MintDockManagerElement extends LitElement {
     static configureDocument(documentRef: Document | null | undefined): void;
     static get observedAttributes(): string[];
     private static instanceCounter;
+    private static readonly TOUCH_LONG_PRESS_MS;
+    private static readonly TOUCH_LONG_PRESS_SLOP_PX;
+    private static readonly TOUCH_PRESS_FEEDBACK_DELAY_MS;
     private documentRef;
     private windowRef;
     private rootEl;
@@ -199,13 +202,36 @@ declare class MintDockManagerElement extends LitElement {
     private captureTabDragMetrics;
     private clearPendingTabDragMetrics;
     /**
-     * Pointerdown handler arms a "may become a drag" gesture. Once the pointer
-     * moves past `threshold` pixels we promote it to an actual pane drag via
-     * {@link beginPaneDrag}; if the user releases first we just clear the
-     * pending tab metrics. All listeners self-clean on resolve so the gesture
-     * stays scoped to a single pointerdown.
+     * Pointerdown handler arms a "may become a drag" gesture. Mouse / pen use a
+     * 5 px distance threshold and arm immediately; touch dispatches to
+     * {@link armPaneDragGestureTouch} which requires a 600 ms stationary hold
+     * (so the user can scroll the tabstrip natively without undocking).
+     * Once armed, both paths converge on {@link beginPaneDrag}. All listeners
+     * self-clean on resolve so the gesture stays scoped to a single pointerdown.
      */
     private armPaneDragGesture;
+    /**
+     * Touch-specific gesture arming. With `.dock-tab` set to `touch-action:
+     * none`, the browser never arbitrates the gesture itself, so JS owns it
+     * from frame 1. Three outcomes from the pending state:
+     *
+     *  - User holds within {@link TOUCH_LONG_PRESS_SLOP_PX} for
+     *    {@link TOUCH_LONG_PRESS_MS} → timer fires → drag arms via
+     *    {@link beginPaneDrag}.
+     *  - User moves past slop and the move is mostly horizontal, and the
+     *    strip's `<ul>` is scrollable → enter `scrolling` mode and drive
+     *    `ul.scrollLeft` from JS for the rest of the gesture (no drag, no
+     *    momentum — direct 1:1 finger follow).
+     *  - User moves past slop in any other direction, releases, or
+     *    pointercancel fires → abandoned, no drag, no scroll. Releases
+     *    under slop fire the synthesized click that drives `tab-activate`.
+     *
+     * `touch-action: pan-x` was the original PRD design but doesn't work:
+     * the policy is frozen at touchstart and `setPointerCapture` doesn't
+     * promote it, so first move after a long-press fires pointercancel and
+     * strands the panel. JS-driven scroll is the only model that holds.
+     */
+    private armPaneDragGestureTouch;
     private beginPaneDrag;
     private preparePaneDragSource;
     private endPaneDrag;