@botiverse/porthole 0.15.2 → 0.15.3
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 +31 -0
- package/dist/check/page-source.js +1 -1
- package/dist/conformance/harness-source.js +1 -1
- package/dist/isolation/served.d.ts +5 -0
- package/dist/isolation/served.js +10 -3
- package/dist/isolation/types.d.ts +6 -0
- package/dist/isolation/types.js +6 -0
- package/dist/platform/focus-guard.d.ts +36 -0
- package/dist/platform/focus-guard.js +82 -8
- package/dist/platform/web.js +10 -2
- package/dist/server/nested.js +2 -1
- package/dist/server/pages.d.ts +9 -2
- package/dist/server/pages.js +28 -8
- package/dist/shell/frame.d.ts +1 -1
- package/dist/shell/frame.js +72 -3
- package/dist/shell/plan.d.ts +5 -0
- package/dist/shell/plan.js +2 -0
- package/dist/shell/runtime.js +259 -0
- package/docs/ADOPTING.md +5 -2
- package/docs/DECISIONS.md +183 -1
- package/docs/DESIGN.md +15 -1
- package/docs/THREAT_MODEL.md +31 -6
- package/package.json +1 -1
- package/src/isolation/served.ts +12 -3
- package/src/isolation/types.ts +7 -0
- package/src/platform/focus-guard.ts +126 -11
- package/src/platform/web.ts +15 -2
- package/src/server/nested.ts +2 -1
- package/src/server/pages.ts +38 -12
- package/src/shell/frame.ts +76 -3
- package/src/shell/plan.ts +7 -0
- package/src/shell/runtime.ts +259 -0
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,37 @@
|
|
|
4
4
|
section); the reasons for every change are in [docs/DECISIONS.md](docs/DECISIONS.md), by the
|
|
5
5
|
P-numbers below.
|
|
6
6
|
|
|
7
|
+
## 0.15.3
|
|
8
|
+
|
|
9
|
+
- **A nested page's real presses count, each of them** (P148, amends P111). A nested page's shell
|
|
10
|
+
knew of a press in the page only as its own activation turning on, and an activation stays on
|
|
11
|
+
for 5 s: a second press in that time, or a press within 5 s of one on the host's page (a
|
|
12
|
+
dialog's Cancel), turned nothing on, and `comments.open` from it was refused ("This needs a
|
|
13
|
+
click"), or a move into the page taken back. The page's runtime now tells its shell each press
|
|
14
|
+
the browser itself made (a mouse down; a finger or pen up; Enter or Space, not held, on a native
|
|
15
|
+
control that isn't editable; a click on one), over a `MessagePort` the shell sends at each load
|
|
16
|
+
and the runtime takes before any content runs. The shell says when it heard the last
|
|
17
|
+
(`porthole/shell/state`: `pressed`, `presses`), and the host takes it as it takes the
|
|
18
|
+
activation turning on: for a second, with no press or key on the host's page since, and under
|
|
19
|
+
P120's and P122's rules. Nothing a page dispatches is a press, no click while a key is down is
|
|
20
|
+
one, and no content holds the port;
|
|
21
|
+
where the runtime can't install all of it, nothing is told and P111's rule stands alone.
|
|
22
|
+
Only for nested pages (`nested: true`): a served page that isn't nested is as before, and in
|
|
23
|
+
full Chromium ADOPTING's advice for it stands (nest it).
|
|
24
|
+
**For a host:** no API change. The nested shell's script and the shell runtime every served
|
|
25
|
+
document inlines change (the nested shell's `script-src` hash with it; `nestedShellResponse`
|
|
26
|
+
and `/server` compute it, as before). Both sides need 0.15.3 for the change to show: the host's
|
|
27
|
+
page (`createHost`) and whatever serves the content origins. Either side alone behaves as
|
|
28
|
+
0.15.2.
|
|
29
|
+
- **The helpers that take host origins check them** (amends P145, after the audit of 0.15.1).
|
|
30
|
+
`statusPage`, `doorResponse`, `doorStatusResponse` and `nestedShellCsp` took `hostOrigins`
|
|
31
|
+
unchecked: `:0` passed, and a string with a `;` went into the CSP header as written. They are a
|
|
32
|
+
host's own configuration, never content's; each helper now throws a `TypeError` on one
|
|
33
|
+
`hostOriginProblem` refuses, as `createServer` and the host kit already did. `isHostOrigin` now
|
|
34
|
+
refuses what `hostOriginProblem` does (it took `:0`, a port past 65535 and a host the URL parser
|
|
35
|
+
rewrites). **For a host:** a content Worker of your own that passed a malformed origin to one of
|
|
36
|
+
these now gets an error where it got a header no browser would match.
|
|
37
|
+
|
|
7
38
|
## 0.15.2
|
|
8
39
|
|
|
9
40
|
- **Marks ride the document's scroll** (P147, amends P104 and P132). A commented passage's
|