[whatwg] Headings and sections, role of H2-H6
privat at ni-po.com
Sat May 1 02:09:19 PDT 2010
On 01.05.2010 04:02, Boris Zbarsky wrote:
> On 4/30/10 2:08 PM, Nikita Popov wrote:
>> I don't know whether I would be happy, if all headings in my document
>> were shown *BIG*, 'cause I use h1 everywhere. I would much more
>> appreciate them to be unstyled. (But this is only personal opinion.)
> Really? Given:
> <h>This is a header</h>
> This is some text after the header.
> The "unstyled" rendering you would see is:
> This is a headerThis is some text after the header.
Yeah, you're right. This would be problematic. This does convince me,
that using <h> is not a good idea.
>> I easily think that using h1 everywhere isn't semantically correct.
>> Especially if the subsections (with their h1s) cannot be redistributed
>> solely it does not make any sense.
> I'm not sure I follow.
I wanted to say, that it does not make sense to me, to use a highest
ranking heading in all sections, subsections, and subsubsubsections,
especially if they cannot be used solely (out of context).
>> But maybe you are right. The html5 spec is already blown up with stuff
>> nobody will ever use (keygen?) enough.
> Amusingly enough, keygen is something I use once a year or so (when my
> user certificate expires), and something that MIT students need to use
> to, say, register for classes (or view their grades, deal with
> bursar's office stuff online, etc, etc). See
> https://ca.mit.edu/ca/certgen (though that will likely require a
> login... that you may not have). See
> http://ist.mit.edu/services/certificates for the various documentation.
I do not deny, that keygen has it's use cases (the "nobody" was
hyperbolic). I only think, that the use cases are *very* rare. It is
overkill to introduce an HTML element therefore. It would be much more
sane to provide a JS API (as Janos proposed.) [I would do it myself, but
I have only very little knowledge on encryption.]
More information about the whatwg