351605 - Very long strings in a textarea causes overlapping characters

Status: RESOLVED WORKSFORME

(Core Graveyard :: GFX, defect)

Description

[Michele Dal Corso]

In Firefox 2.0 beta2 Linux (OpenSuse 10.0):

When you insert a very long string (50000+ chars) like this:
´´´ ... 
generated by some forums when you post strange chars that needs to be encoded (the above string is generated by a long string of ´ character, entity &#180)

it shows the string overlapped, and Firefox slows down significantly.

I'm attaching a screenshot and a simple html to demonstrate the problem.

Comment 1

[Michele Dal Corso]

Attachment: Screenshot

Comment 2

[Michele Dal Corso]

Attachment: HTML test case

Comment 3

[Majken Connor [:Kensie]]

caused by fix to 237085

Comment 4

[Majken Connor [:Kensie]]

not sure if this is wontfix, or if the intention was to go with this behaviour until a better fix presented itself.  cc'ing roc so he can clarify.

Comment 5

[Andrew Schultz]

Isn't this just bug 257660, which has been a problem for a while?

Actually (see bug 257660 comment 16), that bug was probably fixed by bug 237085 for me on trunk.  But that patch went on the 1.8 branch as well and I still see the bug there.

Comment 6

[Robert O'Callahan (:roc) (email my personal email if necessary)]

This didn't really work before bug 237085 was fixed, did it?

Comment 7

[Michele Dal Corso]

I can confirm: the test case of bug 257660 generates in Linux the same behaviour of this bug. The X chars, after increasing the font size, will ovelap (and don'd disappear as stated in the related bug).

Comment 8

[Majken Connor [:Kensie]]

right, that bug was fixed by making them overlap instead of disappear.

Comment 9

[Robert O'Callahan (:roc) (email my personal email if necessary)]

right, then I don't think we're going to fix this on branch, because it's not really a regression. We will fix it on trunk probably via the text rewrite that's happening now.

Comment 10

[Benoit Girard (:BenWa)]

This bug is no longer reproducible in Aurora 6.0a2. It was likely fixed part of another bug. Please reopen if you can reproduce.