W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2010

[Bug 9829] New: <button> should be scoping for the purpose of implicitly closing <p>

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Jun 2010 08:34:13 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9829-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9829

           Summary: <button> should be scoping for the purpose of
                    implicitly closing <p>
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://www.ubuntu.com/desktop/get-ubuntu/download
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


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

-- 
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 Wednesday, 2 June 2010 08:34:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 2 June 2010 08:34:19 GMT