christianliebel left a comment (w3ctag/design-reviews#1242) @dbaron Thanks again for bringing this to us and for your answers to our questions. We’re closing this review as **satisfied with concerns**. The proposal addresses a real, common need: menus are reinvented on many sites, often with poor keyboard and assistive technology support. A built-in, declarative solution is a good fit for the platform. Our remaining concern is the decision not to build on the existing `<menu>` element. We understand the reasoning, but we’d like the decision backed by data, in line with our principles on [extending existing features](https://www.w3.org/TR/design-principles/#new-features) and [compatibility](https://www.w3.org/TR/design-principles/#removing-features). Is there HTTP Archive data or a Chrome use counter for `<menu>`? Was an opt-in mechanism considered? As noted in the labels, the Mozilla and WebKit positions are still pending and the request lacks a Security & Privacy self-review; we’d ask that both be addressed before progressing. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1242#issuecomment-5801555118 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1242/5801555118@github.com>
Received on Wednesday, 23 September 2026 19:34:19 UTC