@jsenv/navi 0.29.416 → 0.29.418
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/dist/dev/jsenv_navi.js +1595 -1103
- package/dist/dev/jsenv_navi.js.map +19 -17
- package/dist/jsenv_navi.js +1566 -1088
- package/dist/jsenv_navi.js.map +19 -17
- package/docs/AI_INSTRUCTIONS.md +13 -6
- package/docs/drag_interactions.md +297 -401
- package/docs/drag_to_travel.md +157 -754
- package/docs/interactions.md +170 -328
- package/docs/mobile_touch.md +35 -0
- package/docs/resource.md +13 -0
- package/docs/route_transitions.md +35 -7
- package/docs/scroll.md +23 -5
- package/docs/state_binding.md +39 -84
- package/package.json +2 -2
package/docs/AI_INSTRUCTIONS.md
CHANGED
|
@@ -79,7 +79,10 @@ to start when unsure which export solves a problem.
|
|
|
79
79
|
map; a pair of routes is animated by `RouteTravel` or by a transition, never
|
|
80
80
|
both; a test waits for the page arriving, never for its address; the page
|
|
81
81
|
being left stays mounted, hidden, until the movement is over (so what it
|
|
82
|
-
registers globally must let the last arrival win
|
|
82
|
+
registers globally must let the last arrival win, and an action it reads
|
|
83
|
+
goes through `useAsyncData`, which leaves a page no longer shown alone —
|
|
84
|
+
`.value` on the action's signals re-renders it hidden); what a transition
|
|
85
|
+
costs.
|
|
83
86
|
Read before animating a navigation, before writing a custom movement, and
|
|
84
87
|
before believing a symptom that only appears once a pair is animated.
|
|
85
88
|
- `view_transitions.md` — what the browser does to any transition an app
|
|
@@ -221,9 +224,10 @@ to start when unsure which export solves a problem.
|
|
|
221
224
|
- `mobile_touch.md` — what Chrome and Safari do with a finger a gesture also
|
|
222
225
|
reads, measured: they commit it to their own pan ~8px in (read a finger's
|
|
223
226
|
intent before that), `touch-action` restarts at every scroller, when the
|
|
224
|
-
click survives, the tap Chrome drops after a touch drag,
|
|
225
|
-
|
|
226
|
-
|
|
227
|
+
click survives, the tap Chrome drops after a touch drag, the capture every
|
|
228
|
+
finger lands with (which `hasPointerCapture` misses on a field), and how to
|
|
229
|
+
reproduce all of it without a device (Chrome's mobile touch emulator, Safari
|
|
230
|
+
in the iOS simulator). Read before reading a finger yourself, and before concluding a
|
|
227
231
|
gesture works because it works with a mouse.
|
|
228
232
|
|
|
229
233
|
### Layout, CSS and text
|
|
@@ -243,8 +247,11 @@ to start when unsure which export solves a problem.
|
|
|
243
247
|
`scroller`, where a list opens and what a search does to where it is, a popup
|
|
244
248
|
that scrolls, hover while scrolling, how a list clips at its rounded corners
|
|
245
249
|
and why a borderless list has none; many rows: `<List.Items>` and the render
|
|
246
|
-
window (`renderBudget`, its `{ initial, after }` form for a list
|
|
247
|
-
a click,
|
|
250
|
+
window (`renderBudget`, its `{ initial, after }` form for a list whose first
|
|
251
|
+
picture is taken — opening in a click, coming back in a route transition —
|
|
252
|
+
counted from the row it opens on; the whole `onScrolledChange` position,
|
|
253
|
+
`visibleCount` included, handed back to open on it; `virtualItemSize`,
|
|
254
|
+
`findText` for Cmd/Ctrl + F beyond the window).
|
|
248
255
|
Read before writing CSS to make something scroll, and before rendering a
|
|
249
256
|
collection as `<List.Item>` children.
|
|
250
257
|
- `mobile_layout_pitfalls.md` — a horizontal overflow inflates the layout
|