279024 - PREformatting tag inconsistency

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[aaron]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

fact: when a certain webpage is created on a mac, the return character is 0d. 
issue: when it is rendered in a <pre> tag, in windows xp firefox, firefox does
not find the expected windows 0d 0a code.  it seems to render the mac 0d code in
a quirky and wrong way.

Reproducible: Always

Steps to Reproduce:
1. go to the web page indicated
2. scroll down to the syllabus part, at the bottom half.
3. compare with opera's and IE's versions, compare also with the actual source code.

Actual Results:  
the text in the <pre> tag is rendered wrong, at line breaks.

Expected Results:  
render the <pre> tag as it should

Comment 1

[Marcel de Haas]

This behaviour also exists on MS Technet pages. The PRE tag renders the right
font (non-proportional, serif) but the linebreaks do not work. I tried to
replicate this issue with files created on Windows (WinXP Pro SP2 32-bit) and
BSD (FreeBSD 4.10-RELEASE-p2 i386) on FireFox 1.0.1 (Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1) to no avail.
The following URL shows the problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324446

When running the page through HTML Validator and CSS Validator the PRE element
seems to be good.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.