Update the definition of "secure context" to spec changes

NEW
Unassigned

Status

()

Product:
Core
Component:
DOM
Importance:
P2
normal
Reported:
2 years ago
Modified:
a year ago

People

(Reporter: bzbarsky, Unassigned, Mentored)

Tracking

({dev-doc-needed})

Version:
Trunk
Keywords:
dev-doc-needed
Points:
---

Firefox Tracking Flags

(firefox50 affected)

Details
(Reporter)

Description

•
2 years ago 
https://github.com/w3c/webappsec-secure-contexts/issues/26 points out that the logic of https://w3c.github.io/webappsec-secure-contexts/#settings-object has changed somewhat to be a bit more restrictive in terms of what's considered a secure context.

We should update to that, and possibly to the sandboxing behavior that is specced there now.
Mentor: bzbarsky
Priority: -- → P2

Comment 1

•
a year ago 
Adding ddn, in case this change requires updates to our description of secure contexts.
Keywords: dev-doc-needed
You need to log in before you can comment on or make changes to this bug.