[Bug 10551] r5032 breaks "<option><button><option>" (</option> implied by second <option> does not close <button>, as <button> is in the special category, and second <option> itself is never processed)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10551


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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-09-26 02:22:44 ---
Same problem occurs for any of the special elements, e.g.
<option><div><option>, and has since long before r5032. The problem is that
</option> is too "weak". Really to make this work as specced, we'd need
<option> to be a special category element.

I've changed <option> to not imply </option> unless the current node is
<option>, which seems less drastic and equally useful from an authoring
perspective.


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: having an implied element get ignored is poor form

-- 
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, 26 September 2010 02:22:46 UTC