10551 2010-09-05 11:26:22 +0000 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) 2010-10-04 14:46:18 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#parsing-main-inbody P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 38476 0 contributor 2010-09-05 11:26:22 +0000 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 39432 1 ian 2010-09-26 02:22:44 +0000 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 39433 2 contributor 2010-09-26 02:23:12 +0000 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