W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2015

Re: [whatwg] <menuitem>: Issue reported by the web developers

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 7 Oct 2015 07:12:16 +0200
Message-ID: <CADnb78giCgEETKPu8D2w0B0pjLQDhQc+5nvXE4C0xFdDPfd+Ug@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: WHATWG <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>, Sanjoy Pal <sanjoy.pal@samsung.com>
On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters <simonp@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?

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.

Received on Wednesday, 7 October 2015 05:12:46 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:35 UTC