Open Bug 1288292 Opened 9 years ago Updated 3 years ago

Update the definition of "secure context" to spec changes

Categories

(Core :: DOM: Security, defect, P3)

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox50 --- affected

People

(Reporter: bzbarsky, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: dev-doc-needed, Whiteboard: [domsecurity-backlog1])

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
Adding ddn, in case this change requires updates to our description of secure contexts.
Keywords: dev-doc-needed
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Component: DOM → DOM: Core & HTML
Depends on: 1269053

We should figure out what remains to be done here.

Mentor: bzbarsky
Flags: needinfo?(ckerschb)

I added this to our RoadMap; moving the bug over to dom:security.

Component: DOM: Core & HTML → DOM: Security
Flags: needinfo?(ckerschb)
Whiteboard: [domsecurity-backlog1]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.