This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

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)
Summary: r5032 breaks "<option><button><option>" (</option> implied by second <option>...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-05 11:26 UTC by contributor
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-09-05 11:26:22 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#parsing-main-inbody

Comment:
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)

Posted from: 113.197.157.134
Comment 1 Ian 'Hixie' Hickson 2010-09-26 02:22:44 UTC 
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
Comment 2 contributor 2010-09-26 02:23:12 UTC 
Checked in as WHATWG revision r5505.
Check-in comment: Parser: change how <option> is parsed to avoid useless implied tokens.
http://html5.org/tools/web-apps-tracker?from=5504&to=5505