Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fenced Frames: Temporarily allow window.fence.reportEvent from iframes
Associated with the FLEDGE origin trial, there is a flag that allows iframes to load urn:uuids. This CL also enables window.fence.reportEvent in that case, to make it easier to test the new APIs. This will be removed when the iframe urn:uuid flag is removed. For implementation reasons, the behavior right now is: - If the invoking frame is in a fenced frame tree, the behavior is the same as before. - If the invoking frame isn't in a fenced frame tree, reportEvent is available only when the invoking frame is an iframe whose document was navigated to a urn:uuid with attached reporting metadata. For some examples: * embedder > iframe1 (urn1) > iframe2 (https) fence.reportEvent works from iframe1 only. * embedder > iframe1 (urn1) > iframe2 (urn2) fence.reportEvent works from iframe1 (to urn1) and iframe2 (to urn2) * embedder > fencedframe1 (urn1) > iframe2 (https) fence.reportEvent works from fencedframe1 and iframe2 (both to urn1) * embedder > fencedframe1 (urn1) > iframe2 (urn2) fence.reportEvent works from fencedframe1 and iframe2 (BOTH to urn1) WICG/turtledove#309 Change-Id: Ie85bfb5264eb1ae78769533b2b8939f3168c8656 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3690741 Reviewed-by: Daniel Cheng <[email protected]> Reviewed-by: Arthur Sonzogni <[email protected]> Reviewed-by: Shivani Sharma <[email protected]> Commit-Queue: Garrett Tanzer <[email protected]> Cr-Commit-Position: refs/heads/main@{#1014688} NOKEYCHECK=True GitOrigin-RevId: 95b0232d46b725c457f406db36de6461a9250e60
- Loading branch information