- From: Tim Connor <timocratic@gmail.com>
- Date: Fri, 30 Mar 2007 15:10:02 -0700
Okay, sorry if there is a bunch of discussion I'm missing on this, but I've never been able to find it, and the archive search showed no discussion relating to this. I feel the LH died an untimely death. I think it's amusing to see the back tracking from that concept inherent in some of the more generalized section/header nesting in the w3c's later specs. I also understand that the more explicit approach shared in these specs will resolve a lot of this and the addition of nav and/or menu, but.... <lh> being returned would be really nice, imho. It would have been really nice if it was in 4.0 and then 1.x, but better late then never. It's always been annoyed at having the choice of bare text (a pain to style and script) in the li, followed by a block element, or a semantically useless span. This would be especially helpful since most of the list elements seem to not be sectioning elements, thus have no way to do the equivalent: <ol> <lh>A list on stuff</lh> <li>I, Item</li> <li> <ol> <lh>Item, the God</lh> <li>Plot synopsis</li> <li>Characters</li> <li>Stunning conclusion</li> </ol> </li> </ol> Maybe I'm just ignorant of how this is supposed to be handled in the new ways, but after years of dealing with the old ways, it was at least worth throwing my hat in the ring once. I think the goofiness of having a 3 deep lh be equivalent to a 1 deep li, in essence, is offset by being able to be so semantically explicit when nesting lists.
Received on Friday, 30 March 2007 15:10:02 UTC