- From: <bugzilla@jessica.w3.org>
- Date: Fri, 18 Feb 2011 23:52:12 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11903 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-18 23:52:12 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 problem is that if you do that then it becomes essentially impossible to automatically style <h1>, and any other manipulation of sections that relies on the DOM and skips out on implementing the (rather complex) outline algorithm can't even get the basics right. I agree that it is problematic when you mix the two models at a sibling level. Not sure what can be done about that. -- 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 Friday, 18 February 2011 23:52:14 UTC