@jsenv/navi 0.29.404 → 0.29.407

package/docs/AI_INSTRUCTIONS.md

@@ -232,8 +232,8 @@ to start when unsure which export solves a problem.
   `:nth-child`, `:empty`) on a container holding navi components.
 - `safe_area.md` — the two inset families, an app narrower than the window
   (`--navi-app-max-width`), `data-navi-safe-area`, which viewport is which under
-  a virtual keyboard (overlaid on Chromium by default:
-  `--navi-keyboard-inset-bottom`). Read before hand-writing an offset to clear a `FixedBar`.
+  a virtual keyboard (overlaid on Chromium only with
+  `enableVirtualKeyboardOverlay()`: `--navi-keyboard-inset-bottom`). Read before hand-writing an offset to clear a `FixedBar`.
 - `scroll.md` — where scrolling happens: `header`/`body`/`footer`, `List`'s
   `scroller`, where a list opens and what a search does to where it is, a popup
   that scrolls, hover while scrolling; many rows: `<List.Items>` and the render

package/docs/safe_area.md

@@ -200,23 +200,27 @@ the keyboard moves depends on the browser.
 | `visualViewport.height`          | yes, except where the keyboard overlays (below) |
 | `--navi-vvh` (tracks the visual) | same as `visualViewport.height`                 |
 
-Wherever the browser has the VirtualKeyboard API (Chromium), navi makes the
-keyboard overlay the page rather than shrink it (`src/layout/virtual_keyboard.js`):
-no viewport shrinks, and the keyboard arrives as `--navi-keyboard-inset-bottom`
-(`env(keyboard-inset-height)`), which `--navi-app-inset-bottom` adds. Firefox,
-Safari, and an app that called `disableVirtualKeyboardOverlay()` shrink the
-visual viewport instead, and `--navi-keyboard-inset-bottom` stays 0. Either way
+By default the keyboard shrinks the visual viewport, on every browser, and
+`--navi-keyboard-inset-bottom` stays 0. Where the browser has the VirtualKeyboard
+API (Chromium), an app can call `enableVirtualKeyboardOverlay()` to make the
+keyboard overlay the page instead (`src/layout/virtual_keyboard.js`): no viewport
+shrinks, and the keyboard arrives as `--navi-keyboard-inset-bottom`
+(`env(keyboard-inset-height)`), which `--navi-app-inset-bottom` adds. Either way
 `--navi-app-height` and the popup ceilings answer the part of the screen left
 visible.
 
 An overlaying keyboard is one the browser no longer scrolls the focused field
 out from under, so navi does: when the keyboard rises or resizes, and when focus
-moves to another field with the keyboard up, the focused field is scrolled to
-the nearest position clear of it. That scroll relies on both paddings — the
-`scroll-padding-bottom` counts the keyboard, and the room to scroll into comes
-from the marked element's `padding-bottom`, or, on a page that marked nothing,
-from a block navi adds at the end of the document for as long as the keyboard
-is up.
+moves to another field with the keyboard up, a focused field that is not fully
+inside the document's `scroll-padding` box is centered in it. Chrome paints an
+autofill/suggestion strip above the keyboard that neither
+`env(keyboard-inset-height)` nor `geometrychange` counts, so
+`scroll-padding-bottom` adds `--navi-keyboard-strip-allowance` on top of the
+keyboard — which also keeps Chrome's own caret-following, as a textarea grows
+under typing, clear of the strip. The room to scroll into comes from the marked
+element's `padding-bottom`, or, on a page that marked nothing, from a block navi
+adds at the end of the document while the keyboard is up — both count the
+keyboard and the allowance.
 
 `position: fixed` — so every `FixedBar` — is laid out against the **layout**
 viewport. Where the visual viewport is what shrinks, a bottom bar therefore

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.404",
+  "version": "0.29.407",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {
@@ -34,7 +34,7 @@
     "preact": "^11.0.0-rc.2"
   },
   "dependencies": {
-    "@jsenv/dom": "0.17.77",
+    "@jsenv/dom": "0.17.79",
     "@jsenv/humanize": "1.8.6",
     "@jsenv/validity": "0.4.5"
   },