On 7 May 2008, at 17:34, Michael Klier wrote:
fantasai wrote:fantasai wrote: Some examples, as requested: <h1><a name="playground" id="playground">PlayGround</a></h1> <div class="level1"> <p>paragraph</p> <ul> <li class="level1"><div class="li">list item</div> </li> </ul> </div> I would ideally write as <div class="section" id="playground"> <h1>PlayGround</h1> <p>paragraph</p> <ul> <li>list item</li> </ul> </div> The two losses of functionality above are: - ID targetting doesn't work in older browsers (NS4 and below) An alternative would be to keep the anchor on the heading. - Can't style the list marker differently, would have to use list-style-image for the blue boxes. An alternative would be to add back an unclassed <div> and style it with li > div.Not quite, removing the anchor link from the header will render the TOCuseless as well.
Not quite. Modern browsers allow fragment identifiers (#<id>) to target id the id values on any element. However, IE6 does have issues with tab position and keyboard based navigation. I forget the possible structures required to get it to play nicely - any change should be reviewed to ensure keyboard navigation in IE6 still works.
A bigger issue is section edit buttons. The section is the div between the headings. At present editable sections can't be nestable. The implications of this change are much wider than leaner html.
The list styling issue is disputable, and has been discussed a couple of timesalready (IIRC).
I don't recall the discussions, but it is an instance where the leaner html results in a significant loss of functionality.
Fantasai, thanks for the couple of examples, but what are the advantages? Even assuming the above examples didn't have downsides, what would be gained by changing?
- Chris -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist