fenced-frame
fenced-frame copied to clipboard
WICG
Proposal for a strong boundary between a page and its embedded content
https://wicg.github.io/anonymous-iframe/#dom-window-credentialless
The existing spec results in a fenced frame navigating directly to the `url` stored in a `FencedFrameConfig` IDL object when navigating to a config built with the `FencedFrameConfig(url)` default constructor....
The budgeting for exfiltration is now based on site instead of origin. It seems that this spec is out of date.
This PR introduces a new algorithm: `Recalculate the untrusted network status of all frames`. This is called whenever a fenced frame marks its network as disabled, and checks to see...
This is a Protected Audience project. We want to collect click time signals in a click handler. This is in a cross-origin subframe. When we use reportEvent API to send...
The [navigate](https://html.spec.whatwg.org/multipage/browsing-the-web.html#navigate) algorithm has changed since we originally monkey patched it. This PR updates our monkey patch to reference the steps as they currently exist. This also cleans up the...
The navigation algorithm has changed since we last patched it. Our patches now reference steps that are now in different places, or steps that no longer exist since they were...
The default `FencedFrameConfig(url)` constructor does not install a fenced frame config in the spec. `FencedFrameConfig(url)` puts a `url` into the `url` slot, and then we can pass in [either a...
See https://chromium-review.googlesource.com/c/chromium/src/+/5385761.
