- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Aug 2011 06:28:44 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13128
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #8 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-14 06:28:44 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:
If the only reason is styling, then we should fix this in CSS. Requiring that
authors wrap random parts of their documents in <div>s just so they can style
them is a failure of the style layer and a layering violation. You shouldn't
have to change the markup to get the look you want.
Furthermore, this massively complicates the processing that tools would have to
do to process lists. Right now it's very simple, you get the element and you
walk its children. If we make the markup at this level arbitrarily complicated,
it's going to cause all kinds of troubles.
Another reason is that it's syntactically dangerous. Can you spot the mistake
here?
<ul>
<li>...
<li>...
<div>
<li>...
<li>...
</div>
<li>...
</ul>
--
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 Sunday, 14 August 2011 06:28:50 UTC