W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2011

[Bug 12609] Allow <ol>/<ul> to have <ol>/<ul> children

From: <bugzilla@jessica.w3.org>
Date: Fri, 06 May 2011 16:16:20 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QINhU-0004ll-Nc@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12609

--- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-05-06 16:16:19 UTC ---
I explained why I think the spec should change here.  The fact that browsers
generate invalid code is not a good argument by itself -- execCommand() will
realistically always generate invalid code in some cases, as a presentational
API -- but I didn't use that argument.  There's no reason the spec shouldn't
change.

Your code is not the same.  <li>foo<ol><li>bar</li></ol></li> and
<li>foo</li><li><ol><li>bar</li></ol></li> have different meanings.  The first
is a single item, which has a subitem.  The second is two separate items, the
first of which has no subitems and the second of which has no content except
one subitem.  I suggest the spec allow <li>foo</li><ol><li>bar</li></ol> as a
synonym for the first case.  That's what I'm having the execCommand() spec
produce right now in this case, for the reasons I gave -- it's easier to work
with for this use-case.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 6 May 2011 16:16:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:09 UTC