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
On Fri, Apr 30, 2010 at 1:57 PM, Eduard Pascual herenva...@gmail.com 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:
section stays as is.
nav becomes
On Fri, Apr 30, 2010 at 11:57 AM, Eduard Pascual herenva...@gmail.com 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 h1-only approach, selecting each level of
heading requires a list of
On 30.04.2010 21:47, Greg Houston wrote:
On Fri, Apr 30, 2010 at 1:57 PM, Eduard Pascualherenva...@gmail.com 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,
On Fri, Apr 30, 2010 at 3:04 PM, Nikita Popov pri...@ni-po.com wrote:
On 30.04.2010 21:47, Greg Houston wrote:
section class=section
nav class=section
aside class=section
article class=section
address class=section
I think this defeats all the purpose of the different sectioning elements.
On Fri, Apr 30, 2010 at 10:02 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Fri, Apr 30, 2010 at 11:57 AM, Eduard Pascual herenva...@gmail.com 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
