Closed Bug 599228 Opened 14 years ago Closed 14 years ago

Firefox ignores CR entity (&#013;) within <PRE> block

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: andrew.harwood, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.8 Safari/534.7
Build Identifier: 4.0b7pre

FF displays one long line instead of breaking up carriage returns when inside a pre block.

eg:


<html>
    <head></head>
    <body>
        <pre>Block one, contains
actual line break</pre>
    <pre>Block two, contains&#013;CR character instead</pre>
    </body>


Reproducible: Always

Steps to Reproduce:
1. Using example html above, create HTML file
2. Open html file with FF 4 beta
3.
Actual Results:  
line with &#013; CR character shows on one line

Expected Results:  
Should be broken over 2 lines

Happens in the latest Chrome beta too, which is interesting :)
The HTML 5 specification indicates that &#013; is no longer a valid character reference. 

Refer to http://www.w3.org/TR/html5/syntax.html#newlines:

>8.1.3.1 Newlines
>
>Newlines in HTML may be represented either as U+000D CARRIAGE RETURN (CR) >characters, U+000A LINE FEED (LF) characters, or pairs of U+000D CARRIAGE >RETURN (CR), U+000A LINE FEED (LF) characters in that order.
>
>Where character references are allowed, a character reference of a U+000A LINE >FEED (LF) character (but not a U+000D CARRIAGE RETURN (CR) character) also >represents a newline.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.