@botiverse/porthole 0.14.16 → 0.14.18

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 CHANGED
@@ -4,6 +4,35 @@
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.14.18
8
+
9
+ - **A set's pages without the Navigation API, and links within a page (P142).** In Safari before 26
10
+ (no Navigation API), every link to another page of a served artifact's set started the display
11
+ again at its entry: the page that opened now says so as it starts, with or without the API. On
12
+ WebKit (18.2 and 26.6), the first link within a page (`#bottom`) started the display again about
13
+ 2.5 s later: WebKit fires the frame's `load` for it, which the host took for content that left. A
14
+ set's page now says it stayed (`porthole/navigating { same: true }`), which the host takes for
15
+ that load only; its watches and subscriptions go on. Hosts change nothing; nothing is loosened.
16
+
17
+ ## 0.14.17
18
+
19
+ - **An app framed by another (P141): `framedBy`.** `createContentHost({ framedBy })` and
20
+ `createServer({ framedBy })` name the origins of an outer page that frames your app (Raft's Deck).
21
+ `frame-ancestors` is checked against every ancestor, so until now each of your frames was blank
22
+ inside it. Each may now be an ancestor of every frame Porthole serves (content, nested pages,
23
+ doors, status, entry and tab-only pages, the authorize route's pages), after the host origins,
24
+ and is never a host: no frame hears or tells it, it is in no page's `data-porthole-hosts` or
25
+ shell's plan, and redirect entry and the handoff stay `appOrigins`' alone. Exact https origins
26
+ (`http://` on loopback); a wildcard, a path, a desktop scheme, an app origin or the content
27
+ domain's site throws. `statusPage`, `doorResponse`, `doorStatusResponse` and
28
+ `nestedShellResponse` take `framedBy` for a content Worker of your own. Without it every response
29
+ is as before.
30
+ - **Security (P141):** a loosening, bounded: the outer origins only in `frame-ancestors`, and
31
+ checked. Where they are set, a page or a nested page's shell says its `*` fallback (a desktop
32
+ scheme among the host origins) only to a parent the engine names as a host origin, so an outer
33
+ page that frames content directly is told nothing by Porthole and heard by nothing; it can hear
34
+ what the content itself says to its parent.
35
+
7
36
  ## 0.14.16
8
37
 
9
38
  - **On a tab the shell asks no host (P139).** A page opened on a tab of its own no longer asks