[html5] Using <section> and <h1> ? Theoretical?

[Chris Rockwell]

(failed to reply-all)

> That's sort of my point. The W3C are denigrating the html5 whatwg outline
> model (<h1> in nested sections) because the outline is a fiction. But what
> do authors lose by using that, instead of <h2-6>?


You as the author may not lose anything; from an authoring perspective you
might gain readability of your markup, albeit only to other developers.
 The point of the warning, as I see it, is to advise the author that if
his/her intention is to be more accessible by using multiple <h1>'s, their
efforts will not only be in vain as no UA's have implemented it (and some
conversations infer they have no intention of doing so), but they could
further confuse agents that have users depending on the accuracy of the
outline.  I fail to see what is unfair about that warning.


Chris Rockwell


On Wed, May 14, 2014 at 12:33 PM, Brian Tremblay <webmaster at tsmchughs.com>wrote:

> On 5/14/14, 9:30 AM, Bruce Lawson wrote:
>
>> On 14 May 2014 17:22, Brian Tremblay <webmaster at tsmchughs.com> wrote:
>>
>>  What does the html 4 outline do?
>>>
>>
>> there isn't such a concept in HTML4
>>
>
> That's sort of my point. The W3C are denigrating the html5 whatwg outline
> model (<h1> in nested sections) because the outline is a fiction. But what
> do authors lose by using that, instead of <h2-6>?
>
> --
> Brian Tremblay
>
> _______________________________________________
> Help mailing list
> Help at lists.whatwg.org
> http://lists.whatwg.org/listinfo.cgi/help-whatwg.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20140514/4ed4b2c9/attachment.htm>