Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On Fri, Apr 30, 2010 at 10:56 PM, Greg Houston wrote: > On Fri, Apr 30, 2010 at 3:04 PM, Nikita Popov wrote: >> On 30.04.2010 21:47, Greg Houston wrote: >>> >>> >>> >>> >>> >>> >> >> I think this defeats all the purpose of the different sectioning elements. >> They want to save code, not let

Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On Fri, Apr 30, 2010 at 11:01 PM, Eduard Pascual wrote: > ... > Putting that together, a section that links to other pages *and* > consists of content that is tangentially related to the content around > it *must* be *both* a nav and an aside. The most blatant example > (which I thought was clear

Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On Fri, Apr 30, 2010 at 10:02 PM, Tab Atkins Jr. wrote: > On Fri, Apr 30, 2010 at 11:57 AM, Eduard Pascual wrote: >> Actually, if we try to "implement" the outlining algorithm in >> the form of selectors that match each level of headings we have: >> On the case that the -only approach, selecting

Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On Fri, Apr 30, 2010 at 3:04 PM, Nikita Popov wrote: > On 30.04.2010 21:47, Greg Houston wrote: >> >> >> >> >> >> > > I think this defeats all the purpose of the different sectioning elements. > They want to save code, not let you state the obvious by class="section" "class" has one more cha

Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On 30.04.2010 21:47, Greg Houston wrote: On Fri, Apr 30, 2010 at 1:57 PM, Eduard Pascual wrote: So, that's enough of a problem statement (at least for now). My suggestion is to clean things a bit: consolidate the sectioning model into a single element+attribute pair, like this: stays as

Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On Fri, Apr 30, 2010 at 11:57 AM, Eduard Pascual wrote: > Actually, if we try to "implement" the outlining algorithm in > the form of selectors that match each level of headings we have: > On the case that the -only approach, selecting each level of > heading requires a list of something raised to

Re: [whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

On Fri, Apr 30, 2010 at 1:57 PM, Eduard Pascual wrote: > So, that's enough of a problem statement (at least for now). My > suggestion is to clean things a bit: consolidate the sectioning model > into a single element+attribute pair, like this: > stays as is. > becomes > becomes > becomes >

[whatwg] The real issue with HTML5's sectioning model (was: "Headings and sections, role of H2-H6" and "Should default styles for h1-h6 match the outlining algorithm?")

I think I already mentioned this before, but seeing how the issues are surfacing again, maybe it's worth to revisit the real *roots* of the problem. Basically, most of the issues with headings boil down to a single fact: the sectioning model is (probably needlessly) over-bloated. Some people will