On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters <sim...@opera.com> wrote:

On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson <i...@hixie.ch> wrote:

On Wed, 26 Nov 2014, Simon Pieters 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.

That's another option, yeah. Probably the best so far if we can't just
power through and break the sites in question. It's not yet clear to me
how many sites we're talking about here and how possible it is to
evaneglise them.

In httparchive http://bigqueri.es/t/analyzing-html-css-and-javascript-response-bodies/442 :

A related issue that has come up is <menu type=context> vs <menu type=popup>.

* 10070 pages use <menu type=context>
* 0 pages use <menu type=popup>
* 100 pages use <menu type=toolbar> or some other value


Based on this I suggest we rename popup to context in the spec.

Simon Pieters
Opera Software

Reply via email to