This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9575 - header lacks footer’s reference to scoping (nearest ancestor sectioning element/body)
Summary: header lacks footer’s reference to scoping (nearest ancestor sectioning eleme...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-22 05:04 UTC by contributor
Modified: 2010-10-04 14:30 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2010-04-22 05:04:23 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-header-element

Comment:
header lacks footer’s reference to scoping (nearest ancestor sectioning
element/body)

Posted from: 221.191.254.72 by w3.org@boblet.net
Comment 1 Oli Studholme 2010-04-22 05:13:14 UTC
The footer element begins “The footer element represents a footer for its nearest ancestor sectioning content or sectioning root element”. The header element doesn’t mention this.

Either both elements should refer to it or neither should. As this ties into the somewhat complex subjects of sectioning and outlines, it may be better to remove the text and add a new field to the elements’ metadata. Something like “Scope: nearest ancestor sectioning element, or entire page”? Alternatively this text could be added at the end of the description as text or as a note.

While header/footer scope should be obvious inside sectioning elements, I think that it applying to the entire page won’t be. It’s association with section/article may lead some authors to assume if they want to use header they need a containing section/article too.

HTH
Comment 2 Ian 'Hixie' Hickson 2010-08-23 23:05:20 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: The distinction is intentional, and reflects differing authoring styles when dealing with headers and footers. The "semantic" part of the <header> is the <h1>s and so forth inside it, and that is what is associated with the nearest ancestor section.