3 ms·

Nope. It's already been solved by HTML spec. Having an H tag it's the same of having the header tag. It doesn't solve any of the problems. see http://imgu

Nope. It's already been solved by HTML spec. Having an H tag it's the same of having the header tag. It doesn't solve any of the problems. see http://imgur.com/a/FnLVb http://imgur.com/a/FnLVb

jaffathecake 10y ago
The <h> proposal is different to the <header> proposal. <header> isn't involved in outline production. The <h> proposal is more like <h1> + sectioning.
Jaruzel 10y ago
Doing it like that means: a) All headers are H1, and styled the same, unless you then start classing up the section and h1 tags accordingly = more complex css than need be. b) not-so-clever page crawlers won't be able to extract the real H1 header that should title the page content.
- deleted 10y ago
  [deleted]
- walterstucco 10y ago
  I was just showing how the DEAFAULT browser's CSS take care of nesting and different importance of H1 tags depending on the context. H1 is already the H you're looking for.
tomphoolery 10y ago
The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? That seemed to be the crux of this article, we don't need numbered headings like that anymore because we have semantic block-level elements like SECTION, HEADER, etc. These elements can be used by the browser to deduce a structured outline from the page, and it's also easier to use said elements when you can think of them as portable components (without resorting to setting CSS classes on everything). The truth is, H1-H6 were useful to screen readers when the web was a lot less complicated. With the component-driven philosophy of today's web development, it's harder to maintain that structure and stay within the confines of 6 possible headings, especially for single-page designs (the ones that scroll, not "single-page apps" made entirely with JS).
- walterstucco 10y ago
  > The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? the N after the H can be seen as the priority where 1 is the highest and 6 the lowest > we don't need numbered headings like that anymore because we have semantic block-level elements like SECTION, HEADER how do you express HEADING > SUBHEADING > SUB SUBHEADING? using classes? nesting tags? > The truth is, H1-H6 were useful to screen readers when the web was a lot less complicated. So in your opinion since the web is more complex now, we should drop perfectly reasonable tags? > it's harder to maintain that structure and stay within the confines of 6 possible headings I can't remember the last time this has been a problem.

Nope. It's already been solved by HTML spec. Having an H tag it's the same of having the header tag. It doesn't solve any of the problems. see http://imgur.com/a/FnLVb http://imgur.com/a/FnLVb

jaffathecake 10y ago

The <h> proposal is different to the <header> proposal. <header> isn't involved in outline production. The <h> proposal is more like <h1> + sectioning.

Jaruzel 10y ago

Doing it like that means: a) All headers are H1, and styled the same, unless you then start classing up the section and h1 tags accordingly = more complex css than need be. b) not-so-clever page crawlers won't be able to extract the real H1 header that should title the page content.

deleted 10y ago
[deleted]
walterstucco 10y ago
I was just showing how the DEAFAULT browser's CSS take care of nesting and different importance of H1 tags depending on the context. H1 is already the H you're looking for.

tomphoolery 10y ago

The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? That seemed to be the crux of this article, we don't need numbered headings like that anymore because we have semantic block-level elements like SECTION, HEADER, etc. These elements can be used by the browser to deduce a structured outline from the page, and it's also easier to use said elements when you can think of them as portable components (without resorting to setting CSS classes on everything). The truth is, H1-H6 were useful to screen readers when the web was a lot less complicated. With the component-driven philosophy of today's web development, it's harder to maintain that structure and stay within the confines of 6 possible headings, especially for single-page designs (the ones that scroll, not "single-page apps" made entirely with JS).

walterstucco 10y ago
> The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? the N after the H can be seen as the priority where 1 is the highest and 6 the lowest > we don't need numbered headings like that anymore because we have semantic block-level elements like SECTION, HEADER how do you express HEADING > SUBHEADING > SUB SUBHEADING? using classes? nesting tags? > The truth is, H1-H6 were useful to screen readers when the web was a lot less complicated. So in your opinion since the web is more complex now, we should drop perfectly reasonable tags? > it's harder to maintain that structure and stay within the confines of 6 possible headings I can't remember the last time this has been a problem.