Bug 32944 – HTML5 <header> and <footer> elements support

• Status: RESOLVED
• Resolution: FIXED
• Component: DOM

[Kent Tamura]

Implement <header> and <footer>.  They have nesting restrictions unlike <nav>, <section>, <article> and <aside>.

[Kent Tamura]

Created attachment 45553 [details]
Proposed patch

[WebKit Review Bot]

style-queue ran check-webkit-style on attachment 45553 [details] without any errors.

[Maciej Stachowiak]

Comment on attachment 45553 [details]
Proposed patch

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.

[Kent Tamura]

(In reply to comment #3)
> (From update of attachment 45553 [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.

[Maciej Stachowiak]

Comment on attachment 45553 [details]
Proposed patch

(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.

[Kent Tamura]

Oh, I have just understood "Content model" is an author requirement. Thank you!
I'll update the patch.

[Kent Tamura]

Created attachment 45610 [details]
Proposed patch

This updated patch is almost equivalent the patches for <section>, <article> and <aside>.
The tests check we *can* nest <header> and <footer> elements.

[WebKit Review Bot]

style-queue ran check-webkit-style on attachment 45610 [details] without any errors.

[Maciej Stachowiak]

Comment on attachment 45610 [details]
Proposed patch

r=me

[WebKit Commit Bot]

Comment on attachment 45610 [details]
Proposed patch

Clearing flags on attachment: 45610

Committed r52846: <http://trac.webkit.org/changeset/52846>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.