Re: [w3ctag/design-reviews] Other Spec Review: HTML menu elements (Issue #1242)

dbaron left a comment (w3ctag/design-reviews#1242)

Regarding data about compatibility with `<menu>`:  i recently [added a use counter](https://chromiumdash.appspot.com/commit/98f1692cad06d5fbd4a1941f13465e5289fd104a) and I think it just shipped to Chrome Beta but not yet Stable.  It should be on Stable in a few weeks and after that [the data](https://chromestatus.com/metrics/feature/timeline/popularity/6004) should be meaningful.  I wasn't around for the beginning of the design discussions, however I think there's a huge amount of hesitation, rightfully, to change the meaning of an element that's been part of HTML for more than 30 years.

I'm less sure about how much an opt-in mechanism was considered but I think one concern may be that an opt-in mechanism is inherently an attribute, and attributes are mutable, whereas an element's tag name is not.  This creates quite a bit of complexity in the DOM interface (much of which does end up exposed to developers), if a single element class needs to support both the old `<menu>` and the new thing, and needs to be able to dynamically switch between them as attributes change.

(I don't think there's anything interesting in the security/privacy review that applies to this feature.)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1242#issuecomment-5801757042
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1242/5801757042@github.com>