fenced-frame
fenced-frame copied to clipboard
WICG
Proposal for a strong boundary between a page and its embedded content
This issue was brought up in https://github.com/WICG/fenced-frame/issues/158. This PR adds official definitions for the `Allow-Fenced-Frame-Automatic-Beacons` and the `Allow-Cross-Origin-Event-Reporting` response headers that are used for cross-origin opt in for their respective...
This adds event handlers for `onfencedtreeclick`, and describes the algorithm for `window.fence.notifyEvent()`, which fires `fencedtreeclick` events from the fenced frame's document to the `HTMLFencedFrameElement` in the embedder. *** Preview |...
See the "Permissions Changes" section of [this document](https://docs.google.com/document/d/1RSufNtL0KKTvmS9ZajJqyhkuxFfnyIW2hnLE9Mb9ehw/edit?usp=sharing) for details. Fenced frames with unpartitioned data access need to be able to allow certain permissions policy-backed features (mainly Shared Storage) in...
Looking at https://github.com/WICG/fenced-frame/pull/152 - I see `Allow-Cross-Origin-Event-Reporting` referenced, but not defined. I can see that it's parsed as a structured field Item, but doesn't say if it's allowed values are...
`Process an attribution eligible response` interface was changed in https://github.com/WICG/attribution-reporting-api/pull/1238. *** Preview | Diff
Fill in the TODO in "report a private aggregation event": https://wicg.github.io/fenced-frame/#report-a-private-aggregation-event This will entail changes to fenced frame config (adding more fields to "fenced frame reporting metadata") https://wicg.github.io/fenced-frame/#fencedframetype-fenced-frame-reporting-metadata and then...
With the work being done for local unpartitioned data access, there are now cases where a fenced frame will be allowed to inherit permissions from its ancestor. This PR updates...