Closed
Bug 306878
Opened 19 years ago
Closed 19 years ago
[Accessibility core only] Focus event not always fired for current focus, after Alt+Tab back to Firefox
Categories
(Firefox :: Disability Access, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
Details
(Keywords: access, fixed1.8)
Attachments
(1 file)
|
856 bytes,
patch
|
parente
:
review+
jst
:
superreview+
asa
:
approval1.8b4-
asa
:
approval1.8b5+
|
Details | Diff | Splinter Review |
Steps: 1. Turn on MSAA Inspect, and watch only focus events, and turn on focus highlighting 2. Optionally, start up accevent.exe event watcher 3. Place focus in location bar 4. Alt+tab twice What happens: Focus is on application window but should be in location bar
| Assignee | ||
Comment 1•19 years ago
|
||
When focus comes back to application root, update gLastFocusedNode to that document node. That's a special case because we don't fire MSAA focus events for the main window, since the system does it for us and that would be redundant. We have to keep gLastFocusedNode updated. The accessibility code has compares the target of focus events with gLastFocusedNode in order to prevent the firing of duplicate focus events.
Attachment #194693 -
Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #194693 -
Flags: review?(parente)
| Assignee | ||
Updated•19 years ago
|
Flags: blocking1.8b5?
Attachment #194693 -
Flags: review?(parente) → review+
| Assignee | ||
Updated•19 years ago
|
Attachment #194693 -
Flags: superreview?(neil.parkwaycc.co.uk) → superreview?(jst)
Comment 2•19 years ago
|
||
Comment on attachment 194693 [details] [diff] [review] Simple patch -- see below sr=jst
Attachment #194693 -
Flags: superreview?(jst) → superreview+
| Assignee | ||
Updated•19 years ago
|
Summary: Focus event not always fired for current focus, after Alt+Tab back to Firefox → [Accessibility core only] Focus event not always fired for current focus, after Alt+Tab back to Firefox
| Assignee | ||
Comment 3•19 years ago
|
||
Comment on attachment 194693 [details] [diff] [review] Simple patch -- see below Low risk fix. Seeking a= for 1.8b4 on the basis that it is only in the accessibility core and does not affect mainstream users.
Attachment #194693 -
Flags: approval1.8b4?
| Assignee | ||
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Attachment #194693 -
Flags: approval1.8b4? → approval1.8b4+
Updated•19 years ago
|
Attachment #194693 -
Flags: approval1.8b4+ → approval1.8b4?
Comment 4•19 years ago
|
||
Comment on attachment 194693 [details] [diff] [review] Simple patch -- see below Lockdown for beta one happened last night and we've got candidates in hand so this will need to wait until first thing in beta two.
Attachment #194693 -
Flags: approval1.8b5?
Attachment #194693 -
Flags: approval1.8b4?
Attachment #194693 -
Flags: approval1.8b4-
Updated•19 years ago
|
Attachment #194693 -
Flags: approval1.8b5? → approval1.8b5+
Updated•19 years ago
|
Flags: blocking1.8b5? → blocking1.8b5+
You need to log in
before you can comment on or make changes to this bug.
Description
•