fenced-frame
fenced-frame copied to clipboard
WICG
Proposal for a strong boundary between a page and its embedded content
https://wicg.github.io/fenced-frame/#dom-fenceevent-eventtype doesn't have any uses that say what values are expected to work in that field. There's one instance of "If event’s [eventType](https://wicg.github.io/fenced-frame/#dom-fenceevent-eventtype) is not "reserved.top_navigation", return.", which implies that...
See https://github.com/WICG/fenced-frame/pull/106#pullrequestreview-1496777120. /cc @gtanzer
The frame size is frozen at first navigation and coerced to the nearest allowed size.
In order to prevent joining information from multiple opaque URLs, or communicating information adaptively into the fenced frame, embedder-initiated navigations should create a fresh slate inside the fenced frame, in...
Specify top-level navigation inside opaque-ads fenced frames using the new reserved target "_unfencedTop", which acts like "_top" but ignores fence boundaries. Decision point: should _unfencedTop act like a normal target...
Currently, [Fenced Frames disallow all Permission policies](https://github.com/WICG/fenced-frame/blob/master/explainer/permission_document_policies.md) for privacy reasons. [Shared Storage](https://github.com/WICG/shared-storage) is going to add its permissions policy as well. The following Shared Storage use cases will benefit from...
Remove fenced frame config mapping when urn iframes are gone (and the construct is no longer necessary)
There are quite a few cases where an opaque ad won't be allowed to load. Developers will have an API to let them know if fenced frame creation will fail...
_unfencedTop: https://chromium-review.googlesource.com/c/chromium/src/+/3763126
This is being filed as a follow-up to https://github.com/WICG/fenced-frame/pull/74, specifically see the comment https://github.com/WICG/fenced-frame/pull/74/files#r1181069647.