W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2012

Re: [whatwg] main element parsing behaviour

From: Simon Pieters <simonp@opera.com>
Date: Wed, 07 Nov 2012 12:51:17 +0100
To: whatwg <whatwg@whatwg.org>, "Steve Faulkner" <faulkner.steve@gmail.com>
Message-ID: <op.wnei7rnwidj3kv@device-23f190>
On Wed, 07 Nov 2012 12:46:36 +0100, Simon Pieters <simonp@opera.com> wrote:

> On Wed, 07 Nov 2012 11:40:57 +0100, Steve Faulkner  
> <faulkner.steve@gmail.com> wrote:
>
>> Hi Anne,
>>
>> That feedback as stated was mainly for Hixie, who dismissed it.
>>
>> I have sought further opinion, but do not have the expertise to know  
>> what I
>> need to do with it.
>>
>> for example, I get the sense that implementers in general do not want to
>> mess with the parsing algorithm, so does that mean. I don't need to put
>> anything in the spec?
>
> That's right.

OTOH, if we wanted <main> to parse like <aside>, we'd add "main" to:

[[
A start tag whose tag name is one of: "address", "article", "aside",  
"blockquote", "center", "details", "dialog", "dir", "div", "dl",  
"fieldset", "figcaption", "figure", "footer", "header", "hgroup", "menu",  
"nav", "ol", "p", "section", "summary", "ul"
]]

and:

[[
An end tag whose tag name is one of: "address", "article", "aside",  
"blockquote", "button", "center", "details", "dialog", "dir", "div", "dl",  
"fieldset", "figcaption", "figure", "footer", "header", "hgroup",  
"listing", "menu", "nav", "ol", "pre", "section", "summary", "ul"
]]

in  
http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#parsing-main-inbody

-- 
Simon Pieters
Opera Software
Received on Wednesday, 7 November 2012 11:51:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT