This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 551
Port "creator context security" (once it's defined). #524
Comments
whatwg/html#1561 landed, FYI. |
@travisleithead will you be looking at this, or do you need me to have a bash? |
Ping - I'll look at this tomorrow if Travis doesn't pick it up to get you over the line for the 20th |
#615 is in flight, currently not building though... |
travisleithead
pushed a commit
that referenced
this issue
Jan 20, 2017
* Issue #524 'creator context security' * Port whatwg/html@a5853c3 Note, workers change in #1561 out of scope in HTML 5.2 - needs to go into workers spec.
Closed with PR#772 |
W3C-HTML-Bot
pushed a commit
that referenced
this issue
Jan 20, 2017
arronei
pushed a commit
to arronei/html
that referenced
this issue
Apr 17, 2017
* Issue w3c#524 'creator context security' * Port whatwg/html@a5853c3 Note, workers change in w3c#1561 out of scope in HTML 5.2 - needs to go into workers spec.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
whatwg/html#1561 defines a new "creator context security" concept, which replaces the "creator
Document
" concept that Secure Contexts relied on back when it existed. It apparently doesn't exist anymore, so.... w3c/webappsec-secure-contexts#37 :)It would be lovely if y'all would port this change over, assuming that your friends and mine at WHATWG accept it.
The text was updated successfully, but these errors were encountered: