On Wed, 07 Oct 2015 07:12:16 +0200, Anne van Kesteren <ann...@annevk.nl> wrote:

On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters <sim...@opera.com> wrote:
Make the end tag optional and have <menuitem>, <menu> and <hr> generate
implied </menuitem> end tags. (Maybe other tags like <li> and <p> can also imply </menuitem>.) The label attribute be honored if specified, otherwise
use the textContent with leading and trailing whitespace trimmed.

This would allow either syntax unless I'm missing something.

File an issue on doing this?

Filed https://github.com/whatwg/html/issues/234 and https://github.com/whatwg/html/issues/235

Are Firefox and Chrome (behind a flag) implementing this feature
identical otherwise? Anything they don't implement from the <menu>
setup? It seems at this point we should cut our losses and remove
unimplemented markup features and defer to custom elements for the
foreseeable future.

Simon Pieters
Opera Software

Reply via email to