@kehto/paja 0.21.3 → 0.22.0
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/README.md +15 -2
- package/dist/browser-host.js +633 -140
- package/dist/browser-host.js.map +1 -1
- package/dist/{chunk-HG2CUTQC.js → chunk-RMYEHOOR.js} +75 -5
- package/dist/chunk-RMYEHOOR.js.map +1 -0
- package/dist/cli.js +1 -1
- package/dist/index.js +1 -1
- package/package.json +5 -5
- package/dist/chunk-HG2CUTQC.js.map +0 -1
package/README.md
CHANGED
|
@@ -59,7 +59,7 @@ warning, when the target would block the sandboxed frame.
|
|
|
59
59
|
|
|
60
60
|
Every drawer section is a flush, independent native accordion: **Pointer** (in
|
|
61
61
|
runtime-pointer mode), **Interfaces**, **ACL**, **Signer**, **Resource servers**,
|
|
62
|
-
then **
|
|
62
|
+
**Messages**, then **Events** last. Headers support Enter/Space, visible keyboard focus and
|
|
63
63
|
state chevrons; bodies keep their padding and live controls when hidden. Sections
|
|
64
64
|
start expanded unless a validated origin-local boolean preference says otherwise.
|
|
65
65
|
The collapsed map uses `kehto:paja:sidebar-sections:v1`, separately from whole-drawer
|
|
@@ -129,7 +129,20 @@ bounded range reads, canonical padded-base64 writes, replace/append/patch,
|
|
|
129
129
|
revisions and preconditions, recursive mkdir/remove, atomic handle moves when
|
|
130
130
|
the browser supports them, and advisory watches over actual storage. Host
|
|
131
131
|
paths and handles never cross the NIP-5D boundary. This implementation follows
|
|
132
|
-
draft [NAP-FS `
|
|
132
|
+
draft [NAP-FS `bd1b9e91`](https://github.com/napplet/naps/blob/bd1b9e912f05203bf38f7a1b04f920744fe6d625/naps/NAP-FS.md).
|
|
133
|
+
|
|
134
|
+
Workspace storage and native pickers have separate browser requirements. Firefox
|
|
135
|
+
can provide OPFS while lacking `showOpenFilePicker`, `showSaveFilePicker`, and
|
|
136
|
+
`showDirectoryPicker`. In that environment, workspace operations remain usable
|
|
137
|
+
and the corresponding picker requests return the canonical `unsupported` result.
|
|
138
|
+
The Interfaces panel shows workspace and open/save/directory picker availability
|
|
139
|
+
separately; the message log names a missing picker API when one caused that result.
|
|
140
|
+
Green `fs:read` and `fs:write` ACL controls indicate permission, not browser API
|
|
141
|
+
support. See the [picker compatibility reference](https://developer.mozilla.org/en-US/docs/Web/API/Window/showOpenFilePicker#browser_compatibility).
|
|
142
|
+
|
|
143
|
+
The focused host regression runs in Chromium and Firefox after `pnpm build`:
|
|
144
|
+
`pnpm exec playwright install firefox`, then
|
|
145
|
+
`pnpm exec playwright test --config playwright.paja-fs.config.ts`.
|
|
133
146
|
|
|
134
147
|
Other domains are equally capability-bound. Relay, outbox, and count require
|
|
135
148
|
live relays; count uses NIP-45 `COUNT` without downloading events. Storage
|