-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Spec] Spec sandbox attribute for <fencedframe> #155
Labels
specification
Additions to specifications
Comments
aarongable
pushed a commit
to chromium/chromium
that referenced
this issue
May 8, 2024
This allows the runtime feature to be overridden by the default state of the base::Feature. Note: Fledge base::Feature is not enabled by default yet, therefore we leave the behavior unchanged for now. Shared Storage API I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/dZ0NRwh7cvs/m/RHvbZNp_AgAJ Fenced Frames I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/tpw8wW0VenQ/m/mePLTiHlDQAJ Topics API I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/PN_aE-X-f9U/m/SweKUn3lBAAJ Private Aggregation API I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/8cKaLstq2QQ/m/JENzsATUBgAJ List of items that are different between I2S and the current implementation: 1. WICG/fenced-frame#155 2. WICG/shared-storage#154 3. https://issues.chromium.org/issues/337055574 Bug: 331926920 Change-Id: I5d2706fabbc6f771d50adfdf358d6daca3322223 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5420588 Reviewed-by: Domenic Denicola <[email protected]> Reviewed-by: Andrew Verge <[email protected]> Reviewed-by: Richard (Torne) Coles <[email protected]> Commit-Queue: Nan Lin <[email protected]> Reviewed-by: Dominic Farolino <[email protected]> Reviewed-by: Yao Xiao <[email protected]> Cr-Commit-Position: refs/heads/main@{#1298072}
This was referenced Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: