<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [whatwg] Reverse ordered
lists</title></head><body>
<div>At 12:53 -0600 23/01/08, Siemova wrote:</div>
<blockquote type="cite" cite>On Jan 23, 2008 12:18 PM, Dave Singer <<a
href="mailto:singer@apple.com">singer@apple.com</a>> wrote:<br>
<blockquote>how about assuming that if the source wants it numbered in
reverse<br>
order, it knows what it is doing, and can tell the browser what<br>
number to start at?<br>
<br>
it still seems the simplest: an attribute that gives the
starting<br>
number (default 1) and an attribute that gives the direction<br>
(increasing or decreasing, default increasing).<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
<br>
True, that's simplest to implement, but why put the onus on the
content author to add things up and specify a start value every time?
Computers are for automating such calculations. If you're reversing a
list, the default value for start shouldn't be 1 anymore; that should
be the ending value, and the starting value ought to be
backwards-engineered from it. This is precisely how a content creator
would expect it to work.<br>
</blockquote>
<blockquote type="cite" cite>I'm surprised at you, being from Apple as
you are. ;) Isn't the idea to make<i> using</i> such a function simple
and intuitive, even if it has to be a little more complicated on the
back-end?</blockquote>
<div><br></div>
<div>complicated is fine. impossible takes a little longer;
if I don't have the end yet, I can't do it right, and the substitutes
all seem ugly.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div>David Singer<br>
Apple/QuickTime</div>
</body>
</html>