- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Oct 2012 05:27:26 +0000
- To: public-html-bugzilla@w3.org
- Message-ID: <bug-19591-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19591 Priority: P2 Bug ID: 19591 CC: public-html@w3.org Assignee: faulkner.steve@gmail.com Summary: Making the main content element a sectioning element QA Contact: public-html-bugzilla@w3.org Severity: normal Classification: Unclassified OS: Windows NT Reporter: ian.html@gmail.com Hardware: PC Status: NEW Version: unspecified Component: maincontent element Product: HTML WG Because both being elements for content, it is inconsistent that complementary content is sectioning element and main content is not. Another reason is about document outline. Please take a look at the markup below: <!DOCTYPE html> <title>blablabla</title> <header> <h1>Branding</h1> <nav> <h1>Navigation</h1> blablabla </nav> <aside> <h1>Search</h1> blablabla </aside> </header> <main role="main"> <h1>Main Content</h1> <section> <h1>Welcome</h1> blablabla </section> <section> <h1>Brief Intro</h1> blablabla </section> </main> <aside role="complementary"> <h1>Complementary Content</h1> <article> <h1>Latest News</h1> blablabla </article> <article> <h1>Recent Comments</h1> blablabla </article> </aside> <footer> blablabla </footer> If the main content element is a sectioning element, the document outline formed by the above code will be clear and hierarchically correct: 1. Branding 1. Navigation 2. Search 3. Main Content 1. Welcome 2. Brief Intro 4. Complementary Content 1. Latest News 2. Recent Comments But if the the main content element is not a sectioning element, the document outline will be confusing and hierarchically incorrect: 1. Branding 1. Navigation 2. Search 2. Main Content 1. Welcome 2. Brief Intro 3. Complementary Content 1. Latest News 2. Recent Comments Both main content and complementary content are content, so they are supposed to be at the same level in document outline. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 18 October 2012 05:27:27 UTC