-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Technical Review: Add documentation for Fenced Frames #27781
Conversation
Preview URLs (29 pages)
Flaws (28)Note! 12 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLs (55)URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
(comment last updated: 2023-12-08 15:33:21) |
Thanks @chrisdavidmills - do you want me to have a look already or should I wait until it's out of draft status? |
It'd be better to wait until it is a) out of draft status, and b) I've got the Google eng folk to have a look at it, as there are still a fait few details here that I'm not sure about. I'll let you know. Cheers! |
I was pinged to take a look at this from Google's perspective, and I'm wondering if you could update the compiled documentation links above (in #27781 (comment)), since they seem outdated now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay. Left a new round of comments. Home stretch!
Thanks for the super-helpful comments @gtanzer; updated, and back to you. |
|
||
```js | ||
const configs = window.fence.getNestedConfigs(); | ||
console.log(configs.length); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might make more sense as an example here to have a different fenced frame, and then do fencedframe.config = configs[0] or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. I've replaced it with something slightly more substantial.
@chrisdavidmills Changes lgtm. I don't see an option to resolve each, maybe because I'm not technically a reviewer. |
Thanks a lot @gtanzer. I have gone through and resolved all the comments that sound like a done deal. There are four left that I think still need input from you:
|
@chrisdavidmills Responded, thanks for surfacing them |
OK @gtanzer, just to let you know, next stage is to get this PR editorial reviewed. I'll close this PR and open up a new one based on the same branch to contain the editorial review. |
Note: This technical review is now completed and approved. For the follow-on editorial review, see #30874
Description
Fenced frames are an integral part of Google's privacy sandbox technologies. Many parts of this set are being made available by default in Chrome 115 (depending on a gradual ramp up to 100% of userbase over the 115 release period).
This PR provides documentation for the
<fencedframe>
element and the APIs that underpin it.See my research document for more details of exactly what changes are expected in the PR.
Motivation
Additional details
Related issues and pull requests