This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It turns out that bug 9496 didn't capture all important aspects of <button>'s scopingness. While it makes sense to make button non-scoping for the purpose of mismatched end tag tokens coming from the tokenizer, <button> should be scoping for the purpose of implicitly closing <p>. That is, <p> should not get closed implicitly in this case: <p><button><h5>Foo</h5></button></p> Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=569528
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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r5158. Check-in comment: Make the implied </p> magic not cross <button> boundaries since doing that breaks a(n invalid) Ubuntu download page. Rename the 'phrasing' category to 'ordinary' since I keep forgetting that 'phrasing' is not an explicit list but is in fact an open-ended list. Merged the 'special' and 'scoping' categories since nothing distinguished them. http://html5.org/tools/web-apps-tracker?from=5157&to=5158