[w3ctag/design-reviews] Mixed content level 2 (#420)

こんにちはTAG!

I'm requesting a TAG review of:

  - Name: Mixed Content Level 2
  - Specification URL: https://w3c.github.io/webappsec-mixed-content/level2.html

  - Explainer (containing user needs and example code)¹: n/a as this is not a new web feature; please see Introduction of spec and advise if a separate explainer would be helpful
  - GitHub issues (if you prefer feedback filed there): https://github.com/w3c/webappsec-mixed-content/issues/

  - Tests: https://cs.chromium.org/chromium/src/third_party/blink/web_tests/http/tests/mixed-autoupgrade/ (need to port to WPT)
  - Primary contacts (and their relationship to the specification): @estark37, @mikewest, @carlosjoan91

Further details:

  - Relevant time constraints or deadlines: Planning to ship in Chrome in early 2020, ideally need approvals in next 6 weeks
  - [X] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The [assessment is here](https://github.com/w3c/webappsec-mixed-content/blob/master/level2_security_privacy.markdown).
  - [X] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - The group where the work on this specification is: WebAppSec

You should also know that...

This change has been running in Chrome as an experiment for several months (currently at 50% of beta channel).

We'd prefer the TAG provide feedback as (please select one):

  - [X] open issues in our GitHub repo for each point of feedback
  - [ ] open a single issue in our GitHub repo for the entire review
  - [ ] leave review feedback as a comment in this issue and @-notify [github usernames]


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/420