[Bug 16364] New: Paragraph: Within 'The "in body" insertion mode' the paragraph 'A start tag whose tag name is "xmp"'. This paragraph causes browser to always handle an xmp tag with a p tag as ending the p tag involved. In default xmp is a block element and this is no pr

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16364

           Summary: Paragraph: Within 'The "in body" insertion mode' the
                    paragraph 'A start tag whose tag name is "xmp"'.  This
                    paragraph causes browser to always handle an xmp tag
                    with a p tag as ending the p tag involved. In default
                    xmp is a block element and this is no pr
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://dev.w3.org/html5/spec/Overview.html
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Paragraph: Within 'The "in body" insertion mode' the paragraph 'A start tag
whose tag name is "xmp"'. 

This paragraph causes browser to always handle an xmp tag with a p tag as
ending the p tag involved. In default xmp is a block element and this is no
problem. But when using 'display: inline' this specification will cause the
first xmp tag in the p tag area to end the paragraph it is in. Subsequent xmp
tags within this p area do not end any p tag. 

The question is whether this rule should take this into account so that xmp
defined as inline will show up proper inline. Example code where the problem
occurs:

<p> This short code <xmp class="shortcode"><form></form></xmp> will break up
the paragraph, but this code <xmp class="shortcode"><form></form></xmp> will
not  break up the paragraph, neither will the following code: <xmp
class="shortcode"><p></p></xmp>. Should the specification be adjusted?
</p>

The question is whether this should be remedied in the specification.

Guus Bonnema, gbonnema@(*spam-prevention*)xs4all.nl.

Posted from: 2001:980:4536:1:92e6:baff:fe68:eb79
User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:10.0.2) Gecko/20100101
Firefox/10.0.2

-- 
Configure bugmail: https://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, 14 March 2012 10:20:56 UTC