- From: TAMURA, Kent <notifications@github.com>
- Date: Mon, 07 Oct 2019 17:13:07 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/428@github.com>
こんにちはTAG! I'm requesting a TAG review of: - Name: ElementInternals's states property and the :state() pseudo class - Specification URL: N/A; The proposal will be a part of DOM/HTML/CSS specifications - Explainer (containing user needs and example code)¹: https://github.com/w3c/webcomponents/blob/gh-pages/proposals/custom-states-and-state-pseudo-class.md - GitHub issues (if you prefer feedback filed there): https://github.com/w3c/webcomponents/issues/738 - Tests: N/A - Primary contacts (and their relationship to the specification): @rakina (an explainer author), @domenic (an explainer author), @tkent-google (implementer) Further details: - Relevant time constraints or deadlines: No concrete deadlines, but we want feedbacks in a month. - [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/webcomponents/pull/844/files?short_path=a981406#diff-a98140661e93c19281370b8c449001f1). - [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: [Web Components](https://github.com/w3c/webcomponents) We recommend the explainer to be in [Markdown](https://github.github.com/gfm/). On top of the [usual information expected in the explainer](https://w3ctag.github.io/explainers), it is strongly recommended to add: - Links to major pieces of multi-stakeholder review or discussion of this specification: https://github.com/w3c/webcomponents/issues/738 - Links to major unresolved issues or opposition with this specification: No major issues, and no opposition. You should also know that... N/A We'd prefer the TAG provide feedback as (please select one): - [ ] open issues in our GitHub repo for each point of feedback - [ ] open a single issue in our GitHub repo for the entire review - [x] leave review feedback as a comment in this issue and @-notify [@rakina, @domenic, @tkent-google] -- 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/428
Received on Tuesday, 8 October 2019 00:13:29 UTC