- From: Daniel Hiester <alatus@earthlink.net>
- Date: Tue, 24 Jul 2001 10:49:43 -0700
- To: "www-html" <www-html@w3.org>
Indentation could be achieved via stylesheets, actually. But, yes, the status-quo on list indentation is to just list a new list element. And <list type="tree"> was sort of discussed here earlier, until I decided to ask the style forum about the aspect of making the tree apearence a function of stylesheets, as the type attribute from html4 is deprecated. No one has answered my question yet. If something like (for example) XHTML 2.0 is parsed as XML, and the namespace/schema/dtd is parsed by the browser, does that mean that one could create a generic LIST element, and the valid XML parsing UA would be able to understand the LIST element? Or what if someone wrote it into an XHTML 1.1 module? Would an XML-parsing UA be able to parse a LIST element? Or is it still status-quo, where all parsing is done as per the programming done by the UA vendor, and loading the namespace/shcema/dtd is irrelevent? But the thought hit me last week that it seems silly to have muiltiple list elements. I could understand the DL element being justified, but in specific, having both UL and OL sounds to me like the element-heavy, tag-soup-friendly HTML, and not the structure-heavy, stripped-down, simplified XHTML that I have come to apreciate. I wouldn't advocate deprecating both of them in favor of a brand new LIST element, but I am confident that one could already use just OL or just UL (whichever tickles your fancy), and use stylesheets to control how you want it to look. I don't think it makes a huge difference whether you state in the markup that it's an ordered list or an unordered list, because the UA will still only render the list in whatever order the author puts it. It's not as though the UA looks at the list items in a UL, and says, "Hmmm, this is an unordered list. Let's randomize the order of the list items!"
Received on Tuesday, 24 July 2001 13:41:54 UTC