Open
Bug 1260840
Opened 9 years ago
Updated 2 years ago
Up and Down work inconsistently in input with and without [autocomplete="off"]
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox47 | --- | wontfix |
firefox48 | --- | fix-optional |
firefox49 | --- | fix-optional |
firefox50 | --- | fix-optional |
firefox51 | --- | fix-optional |
People
(Reporter: arni2033, Unassigned)
References
Details
(Keywords: regression)
>>> My Info: Win7_64, Nightly 48, 32bit, ID 20160326030430
STR:
1. Open attachment 279308 [details]
2. Click in the first input, press Up/Down keys
3. Click in the second input, press Up/Down keys
AR: Up/Down keys do nothing in 1st input (normal) and move caret in input with [autocomplete="off"]
ER: Up/Down should work the same way in both inputs in attachment 279308 [details]
This is regression between 2011-12-23 and 2011-12-24 (presumably bug 669026).
Before that pushlog, Up/Down keys did nothing in <input>s, as expected. Regression range:
> http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c5b90ea7e475&tochange=f63a99195987
:dolske do we care about this in 48?
Flags: needinfo?(dolske)
Comment 2•9 years ago
|
||
I see the same behavior as arni2033 on Windows 10 (ie, the fields are inconsistent). But this is WFM on OS X -- up/down consistently move to the beginning/end of the field. Amusingly, Chrome (on Windows) consistently moves the cursor, whereas IE/Edge consistently does not move the cursor.
This is a regression from 4.5 years ago, so it doesn't need special tracking for 48.
Flags: needinfo?(dolske)
Updated•9 years ago
|
status-firefox47:
--- → wontfix
status-firefox49:
--- → affected
status-firefox50:
--- → affected
Version: Trunk → 12 Branch
Updated•9 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•