@mintplayer/ng-bootstrap 21.23.0 → 21.24.0

package/fesm2022/mintplayer-ng-bootstrap-dock.mjs

@@ -156,6 +156,7 @@ const styles = unsafeCSS(`:host {
   gap: 0.5rem;
   padding: 0.35rem 0.75rem;
   cursor: move;
+  touch-action: none;
   background: linear-gradient(to bottom, rgba(var(--bs-primary-rgb), 0.15), rgba(var(--bs-primary-rgb), 0.05));
   border-bottom: 1px solid var(--bs-primary-border-subtle);
   user-select: none;
@@ -184,6 +185,7 @@ const styles = unsafeCSS(`:host {
   z-index: 2;
   background: rgba(var(--bs-primary-rgb), 0.1);
   transition: background 120ms ease;
+  touch-action: none;
 }
 
 .dock-floating__resizer:hover,
@@ -274,6 +276,7 @@ const styles = unsafeCSS(`:host {
   box-shadow: var(--bs-box-shadow-sm);
   cursor: all-scroll;
   pointer-events: auto;
+  touch-action: none;
   opacity: 0.45;
   transition: background 120ms ease, border-color 120ms ease, opacity 120ms ease;
 }
@@ -314,6 +317,7 @@ const styles = unsafeCSS(`:host {
   display: block;
   padding: 0.5rem 1rem;
   margin: -0.5rem -1rem;
+  touch-action: none;
 }
 
 .dock-tab:active {
@@ -1664,6 +1668,11 @@ class MintDockManagerElement extends LitElement {
                 this.captureTabDragMetrics(event, stack);
                 this.armPaneDragGesture(event, this.clonePath(location), paneName, stack);
                 event.stopPropagation();
+                // Do NOT call event.preventDefault() here. On touch, that suppresses
+                // the synthesized click on the parent .nav-link button — which is how
+                // mp-tab-control fires `tab-activate`. `touch-action: none` on
+                // `.dock-tab` already prevents the browser from arbitrating the
+                // gesture for scroll, so preventDefault would be redundant + harmful.
             });
             // Content wrapper — projected via mp-tab-control's `${tabId}-content`
             // slot only when this tab is active. Holds the dock manager's per-pane