Closed
Bug 190281
Opened 23 years ago
Closed 22 years ago
Focus doesn't skip disabled inputs properly
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
FIXED
People
(Reporter: neil, Assigned: aaronlev)
References
()
Details
(Keywords: regression, Whiteboard: [adt3])
Attachments
(1 file)
|
563 bytes,
patch
|
aaronlev
:
review+
jst
:
superreview+
asa
:
approval1.4b+
|
Details | Diff | Splinter Review |
Steps to reproduce problem:
1. Load the URL
2. TAB to the first input and type some text
3. Press TAB twice
Expected results: First TAB takes you to third input
Actual results: Second TAB takes you to third input
Additional information: The first TAB selects the text as if I just focused it
Comment 2•23 years ago
|
||
i also see this in the preference panes, eg, where there are textfields
associated with a checkbox:
Advanced
Advanced - Mouse Wheel
Offline & Disk Space
P&S - Cookies
neil, do you remember when this last worked? (a general time period is okay
--just want to know how far back to go in order to narrow the bug down.)
Keywords: nsbeta1
| Reporter | ||
Comment 3•23 years ago
|
||
I had to tweak my patch in bug 82547 because of this bug, so I am reasonably
confident that the regression occurred after the patch dated 2002-09-20.
Comment 4•23 years ago
|
||
this regressed sometime btwn the 9/18 (works fine) and 9/24 (broken) builds.
note: the intermediary builds (tested 9/19, 9/23) were broken (could not tab
within Prefs).
| Reporter | ||
Comment 5•22 years ago
|
||
Does this mean we can get rid of lots of disabled attribute checks?
| Reporter | ||
Updated•22 years ago
|
Attachment #115857 -
Flags: review?(jst)
Comment 6•22 years ago
|
||
Comment on attachment 115857 [details] [diff] [review]
Make mozilla ignore disabled elements
I'm no expert in our CSS extensions, but this looks reasonable to me.
Attachment #115857 -
Flags: review?(jst) → review+
| Reporter | ||
Updated•22 years ago
|
Attachment #115857 -
Flags: superreview?(bzbarsky)
Comment 7•22 years ago
|
||
This needs review by aaronl; with jst being the sr, I guess...
And yes, there are places in the event state manager that could maybe skip
attribute checks now; again, check with aaronl.
| Reporter | ||
Updated•22 years ago
|
Attachment #115857 -
Flags: superreview?(jst)
Attachment #115857 -
Flags: superreview?(bzbarsky)
Attachment #115857 -
Flags: review?(aaronl)
Attachment #115857 -
Flags: review+
Updated•22 years ago
|
Attachment #115857 -
Flags: superreview?(jst) → superreview+
Comment 8•22 years ago
|
||
adt: nsbeta1+/adt3
| Assignee | ||
Comment 9•22 years ago
|
||
Comment on attachment 115857 [details] [diff] [review]
Make mozilla ignore disabled elements
r=aaronl
Attachment #115857 -
Flags: review?(aaronl) → review+
| Reporter | ||
Comment 10•22 years ago
|
||
Comment on attachment 115857 [details] [diff] [review]
Make mozilla ignore disabled elements
This low-risk patch ensures that disabled really means disabled.
Attachment #115857 -
Flags: approval1.4b?
Comment 11•22 years ago
|
||
Comment on attachment 115857 [details] [diff] [review]
Make mozilla ignore disabled elements
a=asa (on behalf of drivers) for checkin to 1.4b
Attachment #115857 -
Flags: approval1.4b? → approval1.4b+
| Reporter | ||
Comment 12•22 years ago
|
||
Fix checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 13•22 years ago
|
||
Hey, _can_ we now eliminate those disabled attr checks in the ESM?
Comment 14•22 years ago
|
||
except for a very minor issue (see bug 205576), this bug is fixed.
vrfy'd with 2003.05.13 comm builds.
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Component: Keyboard: Navigation → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•