Closed
Bug 311162
Opened 19 years ago
Closed 19 years ago
extremely long lines are not rendered
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: seth, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
This is a super-weird issue, and I can't understand it for the life of me. Visit
the URL I gave in Firefox 1.5b1. I get nothing but a bunch of spaces... the page
is blank, but the first line is highlightable as what appears to be a bunch of
spaces. There are actually ~ 300 e-mail addresses there. Copy and paste some of
the "blank" text... you'll see e-mails.
No text after this long line is rendered, either, even if the next line is short.
Visit the page in IE. You see a list of e-mail addresses, all on one line,
separated by commas (IE wraps them but they are all one line.)
If you limit the list a bit by attaching the query string "?paid=0", the list
suddenly pops up in Firefox because the line is not as long.
This is as simplified as a testcase as I can get.
Reproducible: Always
Comment 1•19 years ago
|
||
Works for me: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4)
Gecko/20050908 Firefox/1.4
I see no difference in the visibility or amount of content in IE 6 or Fx 1.5b1.
Are you able to reproduce the problem you're seeing in safe mode?
http://kb.mozillazine.org/safe_mode
Reporter | ||
Comment 2•19 years ago
|
||
Yes, the problem is the same in Safe Mode (yes, I'm sure I entered Safe Mode;
the confirmation dialog popped up and told me my extensions were disabled etc.)
However, a friend on 1.0.7 / Linux doesn't have the problem either. I just asked
a friend using 1.5b1 to test and they cannot see the text either.
I could attach a screenshot?
Comment 3•19 years ago
|
||
*** This bug has been marked as a duplicate of 35229 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•