- From: Samuel Weiler <weiler@w3.org>
- Date: Mon, 12 Aug 2019 14:06:57 -0400
- To: tink@tink.uk, public-web-security@w3.org
Thank you for bringing this to our attention. I have filed an issue asking the editors to do a self review and add a security considerations section to the spec: https://github.com/whatwg/dom/issues/776 On 8/8/19 3:27 PM, Léonie Watson wrote: > Hello Web Security, > > The WHATWG publishes a Review Draft of the DOM Standard every six > months. The HTML WG plans to take alternate Review Drafts to W3C > Recommendation, starting with the current DOM Review Draft. > > Once this process is established, we expect wide and horizontal review > to happen on an ongoing basis as the DOM specification evolves in WHATWG > space. For this first attempt we need to do things a little differently > though, and so we're officially inviting wide and horizontal review of > the June 2019 DOM Standard Review Draft [1]. > > Issues identified during wide and horizontal review should be filed > directly on the WHATWG DOM repository [2], but please let the HTML WG > have a pointer to the mechanism or place where you track your issues by > email to public-html@w3.org. > > We expect issues to be opened, discussed, and resolved in WHATWG space, > but the HTML WG can provide an escalation point if one is needed. The > WHATWG FAQ explains how to raise issues there [3]. > > We plan to open the CFC to adopt the DOM Standard Review Draft as W3C CR > in early November, so would appreciate all you can do to turn around > your review by the end of October (sooner if at all possible). > > If you have questions, or if we can provide any guidance on how to file > issues in WHATWG space, please let us know. > > Léonie on behalf of the HTML WG > [1] https://dom.spec.whatwg.org/review-drafts/2019-06/ > [2] https://github.com/whatwg/dom/issues/ > [3] https://whatwg.org/faq#adding-new-features >
Received on Monday, 12 August 2019 18:07:00 UTC