-
Notifications
You must be signed in to change notification settings - Fork 30
Transition to CR. #39
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
Milestone
Comments
@jakearchibald filed #42, which requests normative change to the |
@w3ctag suggests linking to their "Securing the Web" finding: https://www.w3.org/2001/tag/doc/web-https |
mikewest
added a commit
that referenced
this issue
Aug 30, 2016
As requested in the TAG's review of this document in July. #39
This either has follow-ups or is done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we're ready to transition to CR. Perhaps you share that belief?
https://w3c.github.io/webappsec-secure-contexts/CR.html is up for your review.
+1s and emojified responses welcome here. Alternatively, if you think something's not ready yet, file an issue and I'll link it up here.
CfC posted to the list at https://lists.w3.org/Archives/Public/public-webappsec/2016Jul/0032.html.
Discussion of references to WHATWG docs at #9.
The text was updated successfully, but these errors were encountered: