<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hey Ian,<br>
<br>
Your suggestion makes writing <u>portable</u> mark-up difficult,
which I thought we were moving away from with the introduction of
sectioning elems?<br>
<br>
For example I could create the following mark-up in one section of
my website and use it on another page, where the heading may need to
be a h2 instead of a h1:<br>
<blockquote><font face="Courier New, Courier, monospace"><section></font><br>
<font face="Courier New, Courier, monospace">
<h1>Heading</h1></font><br>
<font face="Courier New, Courier, monospace"> <p>Lorem
ipsum dolor sit amet, consectetur adipisicing elit. Minus,
tempore, dolorum, beatae a repudiandae obcaecati officia placeat
ab iusto vero nobis eveniet distinctio dolor totam laborum
recusandae dolore repellat eos.</p></font><br>
<font face="Courier New, Courier, monospace"></section></font><br>
</blockquote>
<br>
... rather than simply using h1 site wide and knowing where ever I
include it - providing it's sectioned - my mark-up snippet will nest
nicely into a sensible document outline, I now have to worry about
heading details :/<br>
<br>
Where can I reference browser support for outline algorithm - I did
think it came with the html5 doctype?!<br>
<br>
Thanks,<br>
<br>
<div class="moz-cite-prefix">On 12/05/2014 23:36, Ian Hickson wrote:<br>
</div>
<blockquote
cite="mid:alpine.DEB.2.00.1405122229500.27549@ps20323.dreamhostps.com"
type="cite">
<pre wrap="">On Fri, 9 May 2014, Micky Hulse wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Ok, so, W3C is changing the language, but what is WHATWG doing (or, have
plans to do)?
</pre>
</blockquote>
<pre wrap="">
As you pointed out, some people are "hating" on <section> and <h1> and so
on. It's not really clear to me why; the concerns haven't really been well
explained IMHO. There's no plan to change any of this in the WHATWG spec.
(I'm especially confused because this style actually comes from XHTML2,
which was championed by the W3C.)
One thing to bear in mind is that in legacy browsers that don't support
style sheets, and in some accessibility tools that haven't yet been
updated to match the HTML spec, the "<section>" elements are "invisible"
(unknown, treated like <div>). This leads to the <h1>s being treated as
page headers in those UAs. To avoid this problem, while we wait for
support to be more widely available, my recommendation is to use <h2>-<h6>
with <section>, as in:
<h1>...</h1>
<section>
<h2>...</h2>
<section>
<h3>...</h3>
...
...instead of:
<h1>...</h1>
<section>
<h1>...</h1>
<section>
<h1>...</h1>
...
The spec defines these as semantically identical, precisely to enable this
transition period. We'll be able to use the <section>/<h1> style without
even this trouble eventually. If you're not interested in targetting those
browsers (e.g. you're just writing something for your own use) then I
wouldn't worry about any of this.
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div id="hcard-Lewis-Dexter-Litanzios" class="vcard">
<div class="org" style="position:absolute; left:-9999px;
top:-9999px;">ldexterldesign</div>
<a class="url" href="http://www.ldexterldesign.co.uk/"
title="ldexterldesign.co.uk"> <img alt="ldexterldesign logo"
src="cid:part1.00010001.00060001@ldexterldesign.co.uk"> </a>
<div class="fn n"> <span class="given-name">Lewis</span> <span
class="additional-name">Dexter</span> <span
class="family-name">Litanzios</span> </div>
<!-- /.fn.n -->
<div>Web Designer & Developer</div>
<a class="email" href="mailto:mail@ldexterldesign.co.uk">mail@ldexterldesign.co.uk</a>
<div class="tel">+44 7504 907 304</div>
</div>
<!-- /.vcard --></div>
</body>
</html>