- From: Kai Ninomiya <notifications@github.com>
- Date: Wed, 02 Jun 2021 12:24:02 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 2 June 2021 19:25:00 UTC
@torgo Of course, we understand it's a huge API :) Are you looking for pointers to content covered by the explainer, or to content in the spec that is not covered by the explainer? The items discussed by the explainer are the ones that we thought would be of greatest interest, both in terms of design scrutiny and for understanding the API at a high level. It's hopefully organized in such a way that you can skip over details as needed to make it more digestible. Of course there are a lot of aspects of the API that are not touched upon by the explainer, but for the most part these are highly domain-specific designs that are constrained by the shape of underlying native APIs, where we don't have that much design freedom. And there's a huge volume of these, so they are hard to summarize in an explainer. -- 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/626#issuecomment-853323304
Received on Wednesday, 2 June 2021 19:25:00 UTC