-
Notifications
You must be signed in to change notification settings - Fork 81
Fenced frames #781
Copy link
Copy link
Closed
Labels
concerns: complexityconcerns: privacyconcerns: securityconcerns: use casesposition: negativeteam: Privacyteam: Securitytopic: HTMLvenue: W3C CGSpecifications in W3C Community Groups (e.g., WICG, Privacy CG)Specifications in W3C Community Groups (e.g., WICG, Privacy CG)
Metadata
Metadata
Assignees
Labels
concerns: complexityconcerns: privacyconcerns: securityconcerns: use casesposition: negativeteam: Privacyteam: Securitytopic: HTMLvenue: W3C CGSpecifications in W3C Community Groups (e.g., WICG, Privacy CG)Specifications in W3C Community Groups (e.g., WICG, Privacy CG)
Type
Projects
Status
Unscreened
Request for Mozilla Position on an Emerging Web Specification
Other information
Fenced frames is a framing isolation primitive designed for maximum isolation between a frame and its embedder, between which no communication is allowed. Compared with iframes, this entails a similar visual experience but radically different processing model. A fenced frame is therefore suitable for (but not required to) hosting cross-site data which must not be joined across contexts. Please note that while the motivation for fenced frames is in part fueled by FLEDGE and Shared Storage, this proposal is entirely independent and stands on its own, and is to be evaluated as such. It can indeed be used independent of those APIs.
/cc @shivanigithub