Closed
Bug 207659
Opened 23 years ago
Closed 22 years ago
Form input and textarea fields do not display extremely long arrays
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
People
(Reporter: mattsch, Unassigned)
Details
Attachments
(1 file)
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
When pasting in or setting the value of input fields and textarea fields with
extremely long arrays, they do not display.
Reproducible: Always
Steps to Reproduce:
| Reporter | ||
Comment 1•23 years ago
|
||
| Reporter | ||
Comment 2•23 years ago
|
||
I have also tested this on
Mozilla 1.4
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030529 and the bug is
still reproducible. On the textarea field, you will need to scroll over to
notice that all of the array is not being displayed.
Comment 3•23 years ago
|
||
WFM on WinXP 2003052808
I see this also LInux 2003053008 and a hours old CVS build witth GTK2/XFT
My CVS build shows this problem by just scrolling over one screen while my
mozilla.org build takes many screens to show this problem.
| Reporter | ||
Updated•23 years ago
|
Component: Form Submission → Layout: Form Controls
Comment 5•23 years ago
|
||
Another way of reproducing the bug is to just copy/paste the following text 14
times in any of the bugzilla text fields. Then press the "Home" key to get back
to the beginning, like if you wanted to change the first character:
ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF ABCDEF
The funny thing here (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4)
Gecko/20030624) is that as soon as I move the mouse over the text field, it gets
displayed properly. As soon as I insert/delete any char, it gets screwed up again.
Comment 6•22 years ago
|
||
Dup of a known bug in rendering very long lines of text....
Whiteboard: DUPEME
Comment 8•22 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•