Long strings rendering badly (either not shown or line wrap is screwed up)

RESOLVED EXPIRED

Status

()

Firefox
General
RESOLVED EXPIRED
13 years ago
13 years ago

People

(Reporter: sharekk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 SUSE/1.0.4-1.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 SUSE/1.0.4-1.1

Long strings of random characters have display issues.  In the example page the
string wraps without a newline, so the page renders looking like there was a
printer jam (the wrapped text appears on the same line as the unwrapped text). 
 By decreasing the length of the DNA sequence it's possible to get it so the
line does not appear at all (though view->source shows that the string is still
there, just not being displayed)  Possibly related to bug 280104, where long
strings are not displayed.

Reproducible: Always

Steps to Reproduce:
1.  Try to view a page consisting of a long string of random characters (example
included)
Actual Results:  
The second half of the text (wrapped text) appeared on the same line as the
first half.

Expected Results:  
Either the line should not have wrapped or it should have wrapped on a second line.

I checked this on Suse 9.3 and Redhat with the same results.  On windows there
were also display issues but not identical ones (the line was not displayed but
appeared when text was highlighted)

Comment 1

13 years ago
same with: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050620
same with: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050618
Firefox/1.0+

WFM with: Firefox 1.0.4 Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE;
rv:1.7.8) Gecko/20050511 Firefox/1.0.4 (confirms OS dependency)

Updated

13 years ago
Blocks: 302294
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.