- From: Dave Tapuska <notifications@github.com>
- Date: Mon, 29 Jul 2019 11:09:39 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/397@github.com>
こんにちはTAG! I'm requesting a TAG review of: - Name: document-access feature policy - Specification URL: HTML Spec PR: https://github.com/whatwg/html/pull/4606 - Explainer (containing user needs and example code)¹: https://github.com/dtapuska/documentaccess - GitHub issues (if you prefer feedback filed there): https://github.com/dtapuska/documentaccess/issues - Tests: pending - Primary contacts (and their relationship to the specification): @dtapuska Further details: - Relevant time constraints or deadlines: None - [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](url). - [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: WHATWG HTML There is some debate in the one PR about the feasiblity of using feature policy for this definition and I believe it is fine. There is some desire to specify feature policies in meta tags but for this definition it is required to be in a header because it changes the agent cluster (which needs to be determined before the document is created). 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/397
Received on Monday, 29 July 2019 18:10:02 UTC