@jsenv/navi 0.29.403 → 0.29.404
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 +5 -2780
- package/dist/dev/jsenv_navi.js.map +2 -23
- package/dist/dev/jsenv_navi_side_effects.js +2818 -12
- package/dist/dev/jsenv_navi_side_effects.js.map +23 -3
- package/dist/jsenv_navi.js +5 -2692
- package/dist/jsenv_navi.js.map +2 -23
- package/dist/jsenv_navi_side_effects.js +2730 -12
- package/dist/jsenv_navi_side_effects.js.map +23 -3
- package/docs/safe_area.md +11 -1
- package/package.json +1 -1
package/docs/safe_area.md
CHANGED
|
@@ -145,7 +145,8 @@ brings its target to.
|
|
|
145
145
|
|
|
146
146
|
Which element scrolls is the app's business, so navi never picks one. `:root`
|
|
147
147
|
gets the `scroll-padding` unconditionally, since the document is the scrollport
|
|
148
|
-
in the common case
|
|
148
|
+
in the common case — and, while nothing is marked, the keyboard's room at its
|
|
149
|
+
end (see below).
|
|
149
150
|
|
|
150
151
|
Beware of making that container scrollable by accident — see
|
|
151
152
|
[mobile_layout_pitfalls.md](./mobile_layout_pitfalls.md).
|
|
@@ -208,6 +209,15 @@ visual viewport instead, and `--navi-keyboard-inset-bottom` stays 0. Either way
|
|
|
208
209
|
`--navi-app-height` and the popup ceilings answer the part of the screen left
|
|
209
210
|
visible.
|
|
210
211
|
|
|
212
|
+
An overlaying keyboard is one the browser no longer scrolls the focused field
|
|
213
|
+
out from under, so navi does: when the keyboard rises or resizes, and when focus
|
|
214
|
+
moves to another field with the keyboard up, the focused field is scrolled to
|
|
215
|
+
the nearest position clear of it. That scroll relies on both paddings — the
|
|
216
|
+
`scroll-padding-bottom` counts the keyboard, and the room to scroll into comes
|
|
217
|
+
from the marked element's `padding-bottom`, or, on a page that marked nothing,
|
|
218
|
+
from a block navi adds at the end of the document for as long as the keyboard
|
|
219
|
+
is up.
|
|
220
|
+
|
|
211
221
|
`position: fixed` — so every `FixedBar` — is laid out against the **layout**
|
|
212
222
|
viewport. Where the visual viewport is what shrinks, a bottom bar therefore
|
|
213
223
|
stays at the bottom of a window the keyboard is covering: it ends up _behind_
|