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

[Bug 13128] Allow wrapping list items in DIV elements

From: <bugzilla@jessica.w3.org>
Date: Wed, 17 Aug 2011 04:09:38 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QtXRi-0001aj-6F@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13128

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #13 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-17 04:09:37 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: 

This isn't really supported by browsers currently. For example, IIRC legacy IE
will ignore </li> so the <div> in the example in comment 8 will end up inside
the <li> even if you include the end tags.

There is no reason fixing this in CSS should take any longer than fixing it in
HTML.

There are several reasons that this is non-conforming in HTML, the main one
being it is massively error-prone.

I disagree with the premise that omitting end tags is bad form. We certainly
should not be ignoring issues relating to omittable end tags on the basis that
authors who fall prey to such problems deserve it for not being proper authors.


(In reply to comment #10)
> 
> It's not purely a styling issue, it's a logical issue.  There's no way to
> indicate that several consecutive li's are logically related, for style or
> script or any other purpose.

What's the use case here? I don't completely follow. Why doesn't the class=""
attribute handle this adequately?

-- 
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 Wednesday, 17 August 2011 04:09:39 UTC

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