- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 09 Sep 2009 13:00:09 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7551 Summary: People are using <section> incorrectly Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec bugs AssignedTo: dave.null@w3.org ReportedBy: simonp@opera.com QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org Time and time again, I see people who use <section> where it shouldn't be used. Almost in all cases, the outline would make sense if all <section> tags would be removed from the markup. Clearly, this is a bug in the spec. I see patterns where people wrap parts of the page in <section> without having headings for them, which creates untitled sections in the outline. Making <section> without a heading not affect the outline would fix this; dropping <section> would fix this; evang to use <div> instead might fix this to some extent. Making the spec not discourage use of <div> and give examples for when to use it might help. I see patterns where people wrap the contents between the <header> and the <footer> (if footer is present) of an <article> in a <section>. Making <section> without a heading not affect the outline would *not* fix this because the article might have sub headings further down. Dropping <section> would fix this. Restricting the content models to somehow catch this case might fix this. Introducing a <content> element might help. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 9 September 2009 13:00:17 UTC