smbls 3.14.860 → 3.14.861
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/CHANGELOG.md +8 -0
- package/dist/smbls.cjs +45 -45
- package/dist/smbls.cjs.map +3 -3
- package/dist/smbls.core.chunk-SZ456M5Z.esm.js +36 -0
- package/dist/smbls.core.chunk-SZ456M5Z.esm.js.map +1 -0
- package/dist/{smbls.core.dropdown-PCM5SZVC.esm.js → smbls.core.dropdown-UVO6TG2P.esm.js} +2 -2
- package/dist/smbls.core.esm.js +1 -1
- package/dist/{smbls.core.lazyParts-SWCTR443.esm.js → smbls.core.lazyParts-ZRE6CGZV.esm.js} +1 -1
- package/dist/{smbls.core.lazyParts-SWCTR443.esm.js.map → smbls.core.lazyParts-ZRE6CGZV.esm.js.map} +1 -1
- package/dist/{smbls.core.sync-WT3G6BPW.esm.js → smbls.core.sync-ET3QQ6Z5.esm.js} +2 -2
- package/dist/{smbls.core.windows-O3PZONYV.esm.js → smbls.core.windows-DQV63PCA.esm.js} +2 -2
- package/dist/smbls.esm.js +45 -45
- package/dist/smbls.esm.js.map +1 -1
- package/dist/smbls.iife-string.js +2 -2
- package/dist/smbls.iife.js +1 -1
- package/dist/smbls.iife.js.map +1 -1
- package/package.json +1 -1
- package/dist/smbls.core.chunk-R4N5YYND.esm.js +0 -36
- package/dist/smbls.core.chunk-R4N5YYND.esm.js.map +0 -1
- /package/dist/{smbls.core.dropdown-PCM5SZVC.esm.js.map → smbls.core.dropdown-UVO6TG2P.esm.js.map} +0 -0
- /package/dist/{smbls.core.sync-WT3G6BPW.esm.js.map → smbls.core.sync-ET3QQ6Z5.esm.js.map} +0 -0
- /package/dist/{smbls.core.windows-O3PZONYV.esm.js.map → smbls.core.windows-DQV63PCA.esm.js.map} +0 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# smbls
|
|
2
2
|
|
|
3
|
+
## 3.14.861
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 9d85f67: A boot that REPLACES a pre-rendered page keeps what the visitor did on the server's page while the app was being built. Just before the server's nodes go, it reads every field the visitor changed (a value typed, an option picked, a box ticked, a radio picked), the focused field with its selection, and the scroll position of every scroller they moved and of the viewport (`document.scrollingElement`). In the task that inserts the app it puts them on the app's matching nodes — matched by the `data-key` chain, the tag and the rank among equal chains; the app's own root key may differ from the server's — and focuses with `preventScroll`. Once the first view is in, each restored field fires `input`, and `change` where the visitor had committed it (a pick, a tick, a text field they had left; the field they are still typing in gets `input` only), so the app's own handlers write its state. Whatever those handlers move in reply (a focus, a scroll to a section, smooth or not) goes back to where the visitor is before a frame shows it. A field at its server default, an element at scroll 0 and a page with nothing focused cost nothing and fire nothing; an untouched field keeps the app's own default. The one-task replace (`firstRender: false`) does the same.
|
|
8
|
+
|
|
9
|
+
Before, the swap threw all of it away: text typed at 1.9 s was gone at a 7.7 s swap, a pick went back to the first option with the app's state on its default, focus fell to `<body>` (the next Space scrolled the page a screen), and the page's scroller went back to 0.
|
|
10
|
+
|
|
3
11
|
## 3.14.860
|
|
4
12
|
|
|
5
13
|
### Patch Changes
|