Bug 3437 – "wrap" attribute not supported on <pre>

• Component: Layout and Rendering
• Status: RESOLVED FIXED

[David Young]

Not much to say, it's a pretty simple tag, though apparently it's a proprietary MS extension to CSS, but that 
doesn't stop people from using it. Looking at html_blockimpl.cpp, there's just no code there to support it.

[Niels Leenheer (HTML5test)]

Additional information:
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/wrap.asp
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/wordwrap.asp

[Dave Hyatt]

I may be wrong, but i think this is equivalent to the new CSS2.1 white-space property value, "pre-wrap."

[Niels Leenheer (HTML5test)]

I think you're right. The CSS 2.1 even gives the following example to mimic 
IE's proprietary wrap parameter: 

    "In addition, the effect of an HTML PRE element with the non-standard "wrap"   
     attribute is demonstrated by the following example:"

     pre[wrap]  { white-space: pre-wrap }

[Eric Seidel (no email)]

We would need a test case.  The css 2.1 test suite we've landed does not seem to have a test for this.

[Joost de Valk (AlthA)]

Created attachment 5716 [details]
testcase

[Joost de Valk (AlthA)]

Added a testcase, even with <pre wrap="soft> and <pre wrap="hard"> in it... Don't know if we should 
support that though.

[Paul Marks]

This is useful for styling <code> tags using CSS; currently just setting white-space: pre; is undesirable, because on small windows (or long lines of code), this forces the code to flow across other parts of the page.

For <code>, the desirable effect is to have "white-space: pre-wrap;" with soft wrapping, though I cannot speak as to whether it's useful to support both hard and soft wrapping...

[Paul Marks]

Regarding my comments in #7:

Looks like I was using <code> incorrectly; I got its default behavior confused with that of <pre>.  However, <pre> still flows text outside of its box for small windows or long lines, which was already known, so please pardon the bump.

[Alexey Proskuryakov]

This looks like it's working now.

[Robert Hogan]

It does look like there's nothing to do in this bug anymore. So please shout if you disagree!