- From: Rossen Atanassov <notifications@github.com>
- Date: Mon, 11 Jul 2022 10:02:22 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 11 July 2022 17:02:36 UTC
@ArthurSonzogni, We will be able to review this if you can provide [an explainer](https://github.com/w3ctag/tag.w3.org/blob/main/explainers/index.md) that puts this in a bit more context. Please remember that although we are often reviewing security-related proposals, we do not share all the back story of this proposal and how it fits together with other technologies. What is the user need that is being serviced here? What kinds of threats does this protect the user from? How can the developer employ this technique? Etc... Lacking use cases we can follow and review, we encourage use of our explainer template in order to capture all the other important bits in a single place - other considerations, code examples, privacy, security and a11y considerations etc. Can you please write one? Also: in your response to question 2 of the Security and Privacy questionnaire it's a little confusing: do you expose, or do you not expose the info specified? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/742#issuecomment-1180650940 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/742/1180650940@github.com>
Received on Monday, 11 July 2022 17:02:36 UTC