Closed
Bug 18583
Opened 25 years ago
Closed 25 years ago
Typing into input fields doesn't scroll when full
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
M12
People
(Reporter: endah, Assigned: buster)
References
()
Details
I noticed this bug on the URL provided - but it occurs on all other pages I've
tried also.
If one types into an input field like the ones present on the bugzilla entry
form, and fills up the field with text... when continuing typing, the text does
not scroll across - it seems to continue typing because when deleting it deletes
the relevant number of characters that were typed... but visually the field
looks like it is scrolling and then jerking back... and the very last character
becomes a mixed up character of the different characters that are being typed.
This is occuring on a build of mozilla from source downloaded at about 11am 10th
November (time according to mozilla CVS). I don't know if it extends to other
builds.
Assignee: leger → joki
Component: Browser-General → Event Handling
QA Contact: leger → janc
Target Milestone: M12
Updated•25 years ago
|
Assignee: joki → rods
Component: Event Handling → HTML Form Controls
Comment 2•25 years ago
|
||
On Windows on a single line text field I'm correctly getting horizontal
scrolling. However on a mutliline text area vertical scrolling is definitely
not working when the field becomes full. Maybe a problem with the gfx
scrollbars or just the field itself? I guess I'm thinking maybe rods on this
one? Or buster? I'll let them figure out who gets it.
Updated•25 years ago
|
Assignee: rods → buster
Comment 3•25 years ago
|
||
This works fine with native scrollbars, it is all hosed with GFX scrollbars.
reassigning to buster.
This bug is a dup of bug #18353.
The bug about vertical scrolling not working with Gfx scrollbars is bug #20107,
which I checked in a fix for yesterday.
*** This bug has been marked as a duplicate of 18353 ***
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 5•25 years ago
|
||
[bugday] verified as a dupe.
You need to log in
before you can comment on or make changes to this bug.
Description
•