@yuneta/gobj-ui 7.23.14 → 7.23.16

package/README.md

@@ -857,7 +857,10 @@ structural rather than cosmetic — and none of them is visible in the CSS:
 - **One finger has to serve three commands, so the press is arbitrated — at
   the RELEASE** (`press_arbiter.js`, pure and tested): moved → drag; still and
   let go quickly → the element's own action; still and held past 500ms → the
-  context menu. Firing the menu on a TIMER instead cannot arbitrate anything,
+  context menu — with a 15ms haptic tick at the 500ms mark, which is a NOTICE
+  and not the decision (a finger that buzzes and then carries the node away
+  still gets its drag). Firing the menu on a TIMER instead cannot arbitrate
+  anything,
   because at the moment it fires the gesture is not over: it opened while
   `drag-element` was already carrying the node, so one press meant both things
   and the menu sat over a card running away underneath it. Two more things the

package/dist/gobj-ui.cjs.js

@@ -9775,7 +9775,15 @@ function install_long_press_contextmenu(graph, options) {
 	let state = touch_state_of(graph);
 	let pending = null;
 	let disarm = () => {
-		pending = null;
+		if (pending) {
+			clearTimeout(pending.tick);
+			pending = null;
+		}
+	};
+	let announce = () => {
+		if (!pending) return;
+		if (state.multi) return;
+		navigator.vibrate?.(15);
 	};
 	let fire = (event) => {
 		state.long_press_click = true;
@@ -9805,7 +9813,8 @@ function install_long_press_contextmenu(graph, options) {
 			x,
 			y,
 			t0: Date.now(),
-			event: Object.assign({}, event)
+			event: Object.assign({}, event),
+			tick: setTimeout(announce, 500)
 		};
 	};
 	let on_move = (event) => {
@@ -9821,6 +9830,7 @@ function install_long_press_contextmenu(graph, options) {
 	};
 	let on_up = (event) => {
 		let press = pending;
+		if (press) clearTimeout(press.tick);
 		pending = null;
 		if (!press) return;
 		if (state.multi) return;

package/dist/gobj-ui.es.js

@@ -9770,7 +9770,15 @@ function install_long_press_contextmenu(graph, options) {
 	let state = touch_state_of(graph);
 	let pending = null;
 	let disarm = () => {
-		pending = null;
+		if (pending) {
+			clearTimeout(pending.tick);
+			pending = null;
+		}
+	};
+	let announce = () => {
+		if (!pending) return;
+		if (state.multi) return;
+		navigator.vibrate?.(15);
 	};
 	let fire = (event) => {
 		state.long_press_click = true;
@@ -9800,7 +9808,8 @@ function install_long_press_contextmenu(graph, options) {
 			x,
 			y,
 			t0: Date.now(),
-			event: Object.assign({}, event)
+			event: Object.assign({}, event),
+			tick: setTimeout(announce, 500)
 		};
 	};
 	let on_move = (event) => {
@@ -9816,6 +9825,7 @@ function install_long_press_contextmenu(graph, options) {
 	};
 	let on_up = (event) => {
 		let press = pending;
+		if (press) clearTimeout(press.tick);
 		pending = null;
 		if (!press) return;
 		if (state.multi) return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yuneta/gobj-ui",
-  "version": "7.23.14",
+  "version": "7.23.16",
   "type": "module",
   "main": "dist/gobj-ui.cjs.js",
   "module": "dist/gobj-ui.es.js",

package/src/g6_touch_gestures.js

@@ -65,7 +65,7 @@ import {
     register,
 } from '@antv/g6';
 
-import {press_moved, classify_press} from "./press_arbiter.js";
+import {press_moved, classify_press, LONG_PRESS_MS} from "./press_arbiter.js";
 
 
 /***************************************************************
@@ -372,10 +372,36 @@ export function install_long_press_contextmenu(graph, options)
 
     let enable  = options?.enable;
     let state   = touch_state_of(graph);
-    let pending = null;         /* {x, y, t0, event} */
+    let pending = null;         /* {x, y, t0, event, tick} */
 
     let disarm = () => {
-        pending = null;
+        if(pending) {
+            clearTimeout(pending.tick);
+            pending = null;
+        }
+    };
+
+    /*
+     *  The one thing deciding at the RELEASE costs: while the finger
+     *  is down, nothing on the screen says the menu is now what
+     *  letting go would give you.  A tick of haptics says it.
+     *
+     *  It is a NOTICE, not the decision -- the arbitration is still
+     *  entirely in `on_up`.  So a finger that buzzes and then carries
+     *  the node away gets its drag, exactly as if it had never
+     *  buzzed; the tick only reports what the press is worth at the
+     *  moment it crosses the line.  (Where there is no vibrator --
+     *  iOS Safari, a desktop -- `vibrate` is simply absent and this
+     *  is a no-op.)
+     */
+    let announce = () => {
+        if(!pending) {
+            return;
+        }
+        if(state.multi) {
+            return;
+        }
+        navigator.vibrate?.(15);
     };
 
     let fire = (event) => {
@@ -437,6 +463,7 @@ export function install_long_press_contextmenu(graph, options)
             y:     y,
             t0:    Date.now(),
             event: Object.assign({}, event),
+            tick:  setTimeout(announce, LONG_PRESS_MS),
         };
     };
 
@@ -460,6 +487,9 @@ export function install_long_press_contextmenu(graph, options)
 
     let on_up = (event) => {
         let press = pending;
+        if(press) {
+            clearTimeout(press.tick);
+        }
         pending = null;
         if(!press) {
             return;

package/src/yui_toolbar.css

@@ -6,6 +6,15 @@
     width: 100%;
     height: auto;
     position: relative;
+    /*  The toolbar is often a flex item sharing its row with a pinned
+     *  control (a back link, a title). A flex item's `min-width:auto`
+     *  resolves to the CONTENT minimum, and the sections inside are
+     *  `flex-shrink:0; white-space:nowrap` — so the toolbar refuses to
+     *  shrink, the row overflows, and the scroll container never sees an
+     *  overflow of its OWN: both arrows stay hidden while the items are
+     *  clipped by an ancestor. Alone on its row nothing shrinks and the
+     *  bug hides, which is why it only shows up once integrated. */
+    min-width: 0;
 }
 
 .yui-horizontal-toolbar-container {