[Webkit-unassigned] [Bug 32944] HTML5 <header> and <footer> elements support
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Dec 29 07:41:32 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=32944
Maciej Stachowiak <mjs at apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45553|review? |review-
Flag| |
--- Comment #5 from Maciej Stachowiak <mjs at apple.com> 2009-12-29 07:41:32 PST ---
(From update of attachment 45553)
(In reply to comment #4)
> (In reply to comment #3)
> > (From update of attachment 45553 [details] [details])
> > Nesting <footer> inside <header> or <footer> (or vive versa) is an authoring
> > conformance error, but I don't believe it is supposed to result in any parser
> > error fixup. I do not see any such requirement in the HTML5 parsing algorithm
> > anyway. r- for now but please resubmit if you can cite a source for that
> > requirement.
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-header-element
> 4.4.8 The header element
> ...
> Content model:
> Flow content, but with no header or footer element descendants.
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-footer-element
> 4.4.9 The footer element
> ...
> Content model:
> Flow content, but with no header or footer element descendants.
Those are authoring requirements (i.e. a document violating these is
nonconforming), not implementation requirements (there is no requirement to
enforce these conditions at parse time or otherwise.
The only error corrections that should be done are those required by section
9.2:
http://dev.w3.org/html5/spec/Overview.html#parsing
Please keep this in mind when implementing additional new HTML elements. The
content models in general do *not* result in parser behavior changes.
Please resubmit with the parser changes removed and with correct tests.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list