- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Apr 2014 11:23:21 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003 --- Comment #20 from steve faulkner <faulkner.steve@gmail.com> --- > steve faulkner: > > I think it makes sense for the HTML5.0 spec match reality… while the 5.1 spec can continue to reflect future, possible implementations. > > This means the outline model becomes backwards compatible, which is a no-go. > The new outline model was introduced with sectioning elements, we shouldn't > have one without the other. you may be misunderstanding, currently all browsers that implement acc API semantics for headings implement: h1 role=heading level=1 ... h6 role=heading level=6 The HTML5.0 CR spec is meant to reflect interoperable implementations, thus the dropping features that don't currently have interop implementations (see https://www.w3.org/Bugs/Public/show_bug.cgi?id=24812). It has been agreed that the outline algorithm (http://www.w3.org/html/wg/drafts/html/master/sections.html#outlines) does not have any browser interop requirements and therefore will stay in 5.0 and live on in 5.1. The requirements to implement the separate acc layer part has no interop implementations and is the subject of this bug. If the acc layer part gets interop implementations before HTML 5.0 becomes a rec then it will not be removed, if not it will. It will remain in 5.1 awaiting further discussion/ changes/implementation. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 22 April 2014 11:23:22 UTC