@liorean:
We're getting somewhere! You suggest that separators are an aberration,
something inherently ambiguous (and this ambiguity is not desired) and
we should use this opportunity to get rid of it.
The problem, again (if I may be so bold), is that you don't actually
believe the horizontal rule was ever useful. Instead, like many people
arguing against it, you suggest that all instances of its use are in
fact better replaced with alternatives.
In your example you suggest that these separators denote depth, coming
at the end of nested containers - Rob used them as objects appearing
above headings (and yet they were properties of whichever element
preceded the headings): You're giving us crisps when we want chocolate,
and adding chocolate flavouring to the crisps isn't going to make anyone
happy!
If I'm to play this game (may as well), I would suggest this:
<div class="grouping">
<p></p>
<p></p>
<p></p>
</div>
<div class="grouping">
<p></p>
</div>
.grouping + .grouping:before{content: "[separator]"}
This is better than Rob's and your examples because it doesn't assume
the separator is incidental to the presence of other objects, which
cause some kind of separation anyway.
I think the 'grouping' element is still unnecessary - it creates a
superfluous element. With this method, the author would have to be in a
'grouping' at all times, and would create a separation by closing it and
starting a new one - but the author shouldn't have to create the
grouping in the first place, to account for the fact that they may at
some point desire a separator.
I use this example to prove to points:
1) Semantically, the separator object does not rely on the attributes or
pre-defined relationships of other elements. Therefore it needs its own
specific indicating element.
2) The simplest, cleanest and most logical way to implement this element
is to have a literal separator tag.
Regards,
Barney
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
