fenced-frame
fenced-frame copied to clipboard
WICG
Proposal for a strong boundary between a page and its embedded content
It’s great to read through the detailed privacy considerations, thank you! In some applications of Fenced Frames, like Turtledove, it is important to ensure that the content renders in a...
The 'src' allowlist is a feature unique to iframes and fenced frames that, if set, only allows a given feature for the origin loaded in the src/config attribute. This is...
This PR specs the following behavior: - Setting the "Origin" header to the origin of the frame that invoked `reportEvent()` for destination URL events. - Setting the "Origin" header to...
Keeping the core fenced frames functionality in the spec and moving the consumer API specific parts to the respective APIs that can then link into the core fenced frames spec....
Essentially the equivalent of this CL: https://chromium-review.googlesource.com/c/chromium/src/+/4774259 Moving focus into a fenced frame should require user activation by default, unless explicitly specified otherwise.
A fenced frame should not be considered to have its network revoked until all its descendants have their network access revoked as well.
This issue blocks https://github.com/WICG/fenced-frame/issues/165
Do something similar to https://github.com/WICG/fenced-frame/pull/148 but for _unfencedTop and popups
This will require a change to the WPT web driver + an RFC opened for it.