[Bug 16364] 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

Guus <gbonnema@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |gbonnema@xs4all.nl
         Resolution|WONTFIX                     |

--- Comment #2 from Guus <gbonnema@xs4all.nl> 2012-03-14 11:52:22 UTC ---
Please reconsider. The problem occurs when defining the <xmp> tag as inline.
This normally causes an element to be treated as equal to inline. 

Due to the specification paragraph at issue here, this is not the case when the
<xmp> tag is subordinate to a <p> tag. Despite the inline specification, the
<xmp> tag is specified to have an end tag (</p>) inserted. Subsequent inline
<xmp> tags are not affected, because the specification only indicates the
end-tag insertion for <p> tags.

When the inline <xmp> tags are subordinate to another block element (like <h1>
or <h2>) this is not the case and all inline <xmp> tags are treated like
inline.

It is not CSS that causes the problem, but the specification paragraph at issue
here, that specifically states to insert and ending paragraph tag. The result
is that the inline <xmp> is not treated equal to other inline elements.

I quote the paragraph below.

<quote>
A start tag whose tag name is "xmp"                                             
          If the stack of open elements has a p element in button scope, then
act as if an end tag with the tag name "p" had been seen.                       

          Reconstruct the active formatting elements, if any.                   

          Set the frameset-ok flag to "not ok".                                 

          Follow the generic raw text element parsing algorithm.               
</quote>

So you can see, that the specification causes the problem, not CSS.

I respectfully request you to reconsider.

-- 
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 11:52:30 UTC