[Bug 25003] modify required heading mappings to reflect reality

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003

--- Comment #29 from James Craig <jcraig@apple.com> ---
(In reply to steve faulkner from comment #23)
> (In reply to James Craig from comment #12)
> > 
> > It is also specified in a way that ensures the new method is incompatible
> > with previous authoring practices. 
> 
> If the correct (old style) heading structure is used in conjunction with the
> sectioning it is backwards and forwards compat, the evangelizing of all h1's
> is the issue, which I have tried to mitigate by modding the advice in the
> spec.

Potentially, but depending on how the author crafted it, there may be different
heading levels exposed to different platforms or in different browsers, or when
the section was included using a different manner. 

The validator may be able to mitigate some of this by determining the section
level computation and then throwing a warning if it doesn't match up with the
expectation, but again, this is more work than it's worth. A perfectly nested
heading structure is nice-to have, but an incorrectly nested heading structure
doesn't cause any harm to any real category of user that I know of.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 24 April 2014 05:30:42 UTC