@jsenv/navi 0.29.520 → 0.29.521
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/drag_to_travel.md +4 -2
- package/docs/mobile_touch.md +4 -2
- package/package.json +2 -2
package/docs/drag_to_travel.md
CHANGED
|
@@ -29,8 +29,10 @@ the pointer inside a box that travels.
|
|
|
29
29
|
a diagonal would ask for two travels at once when only one screen can arrive.
|
|
30
30
|
The reading leans towards the box's own axis — a thumb swiping sideways moves
|
|
31
31
|
along an arc, and its first pixels lean off-axis far more than the swipe does
|
|
32
|
-
— so the cross axis takes the press only when it clearly dominates
|
|
33
|
-
|
|
32
|
+
— so the cross axis takes the press only when it clearly dominates. Where
|
|
33
|
+
something under the finger scrolls on that axis, the page included, the
|
|
34
|
+
reading is even, the way the browser's is: a scroll that wobbles stays a
|
|
35
|
+
scroll, and a swipe whose first pixels are steeper than 45° scrolls too. A
|
|
34
36
|
finger's 6px is a deadline rather than a feel: the browser commits a touch to
|
|
35
37
|
its own pan about 8px in, and whatever is read after that is read about a
|
|
36
38
|
pointer it has already cancelled (see
|
package/docs/mobile_touch.md
CHANGED
|
@@ -56,8 +56,10 @@ axis: the browser measures its slop as a distance, and a per-axis threshold is
|
|
|
56
56
|
up to 1.4 times later on a diagonal. Waiting for more evidence is not
|
|
57
57
|
available, because whatever is read after the browser's moment is read about
|
|
58
58
|
a pointer that has already been cancelled. It is why a travel reads a finger at
|
|
59
|
-
6px,
|
|
60
|
-
evenly
|
|
59
|
+
6px, before the browser reads the same pixels evenly: leaning towards its own
|
|
60
|
+
axis where nothing scrolls on the other one, evenly where something does, and
|
|
61
|
+
waiting for the browser's own pixels when that reading says the pan is the
|
|
62
|
+
browser's (see [drag_to_travel.md](./drag_to_travel.md#what-the-rules-are)).
|
|
61
63
|
|
|
62
64
|
Whether a `touchmove` can be refused at all is settled even earlier, when the
|
|
63
65
|
finger lands: the non-passive listener that will refuse must already be on the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@jsenv/navi",
|
|
3
|
-
"version": "0.29.
|
|
3
|
+
"version": "0.29.521",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Library of components including navigation to create frontend applications",
|
|
6
6
|
"repository": {
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"preact": "^11.0.0-rc.2"
|
|
35
35
|
},
|
|
36
36
|
"dependencies": {
|
|
37
|
-
"@jsenv/dom": "0.17.
|
|
37
|
+
"@jsenv/dom": "0.17.101",
|
|
38
38
|
"@jsenv/humanize": "1.8.11",
|
|
39
39
|
"@jsenv/validity": "0.4.7"
|
|
40
40
|
},
|