docs(docs): DEPLOY.md: the import worker under the CSP and the Firefox 114 line (OD-1)
This commit is contained in:
1 parent
6d1cce6e06
commit
8924d50edf
1 file changed
+14
@@ -672,6 +672,20 @@ blocked). Browser floor for the keyword: Chrome 97, Firefox 102, Safari 16
|
||||
served for 1.18 MB raw, D-R13 budget 600 KB). A proxy in front must pass
|
||||
`Content-Encoding` through and keep the `application/wasm` type.
|
||||
|
||||
Since R4 the PDF import runs in a module worker (`/assets/import.worker-*.js`,
|
||||
a same-origin hashed file that `script-src 'self'` already allows; no
|
||||
`blob:`, no inline worker): the worker's response carries the same policy, so
|
||||
the keyword is required for the import too. Without it the import answers
|
||||
« Le moteur de lecture n'a pas pu être chargé » and nothing else changes. The
|
||||
CSP needs no other change. Browser support of the import, apart from the
|
||||
application's floor above: module workers need Firefox 114 or later (Chrome
|
||||
80, Safari 15); the import already needed Firefox 113 and Safari 16.4 before
|
||||
R4 (`DecompressionStream`), so Firefox 113 is the one version that loses it
|
||||
(owner decision OD-1, `docs/development/RUST.md` §10). The worker never
|
||||
fetches the module when the page's runtime already holds it (the compiled
|
||||
module is posted), so an import works offline once the editor has loaded
|
||||
the engine, as before.
|
||||
|
||||
---
|
||||
|
||||
## Health checks
|
||||
|
||||
Reference in new issue
Block a user