- From: <bugzilla@jessica.w3.org>
- Date: Fri, 08 Oct 2010 08:32:49 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10824 --- Comment #6 from fantasai <fantasai.bugs@inkedblade.net> 2010-10-08 08:32:46 UTC --- > Is there reason to believe HTML could change the default behavior safely, even > though CSS cannot? Yes. The case affected here is fairly rare, and in most cases the current rendering is awkward and has to be worked around by use of <span> or <div> tags inside the <li>. While I don't have any data for you, it seems likely that content-compatibility is not a concern here. For CSS, the argument for not changing is that we have full interop on the current initial value, and since the behavior is useful for non-list-item cases, it does not make sense for us to attempt to change all implementations. It makes more sense for us to introduce a switch in CSS3, and suggest that the new value be used by default for <li> items. (The CSSWG already has formal resolutions responding to this issue that we will not alter the behavior specced in CSS2.1.) I agree that this is not an HTML5 spec issue except insofar as the new value should be adopted in the recommended CSS defaults once it is specced out. So imo fixing this depends on an update to CSS3 Lists. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug.
Received on Friday, 8 October 2010 08:32:50 UTC