Skip to content

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

Closed
mikewest opened this issue Jul 19, 2016 · 4 comments
Closed

Transition to CR. #39

mikewest opened this issue Jul 19, 2016 · 4 comments
Milestone

Comments

@mikewest
Copy link
Member

mikewest commented Jul 19, 2016

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.

@mikewest mikewest added this to the CR milestone Jul 19, 2016
@mikewest
Copy link
Member Author

@titanous noted #40, which won't have any normative effect, but is an important editorial change to make before CR.

@mikewest
Copy link
Member Author

@jakearchibald filed #42, which requests normative change to the noopener bits of the spec.

@mikewest
Copy link
Member Author

@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
@annevk
Copy link
Member

annevk commented Oct 10, 2017

This either has follow-ups or is done.

@annevk annevk closed this as completed Oct 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants