- From: Lea Verou <notifications@github.com>
- Date: Wed, 20 Jul 2022 08:43:34 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 20 July 2022 15:43:56 UTC
Hi there, We looked at this today during our plenary and we have no objection to moving this feature forward. Some of us are very familiar with the work, and some of us are very familiar with the strong developer need for this feature and its multi-stakeholder support. While we did not do a deep dive on it in the TAG itself, we do not see any architectural concerns and are happy to see this move forward. In the future, please include explainers with review requests. While better than nothing, an MDN article is not a substitute for an explainer, as it doesn't satisfy all requirements for what an explainer needs to contain. E.g. not every MDN article includes use cases, and this one does not. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/712#issuecomment-1190446984 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/712/1190446984@github.com>
Received on Wednesday, 20 July 2022 15:43:56 UTC