Closed
Bug 349709
Opened 18 years ago
Closed 18 years ago
Focus events not always fired after window:activate
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 368322
People
(Reporter: parente, Assigned: aaronlev)
References
Details
(Keywords: access)
In gtk/gail, the widget that last had focus before its parent top-level window was deactivated always fire focus events when the top-level window is reactivated. Firefox currently only fires focus events on window:activate if the focus changed programmatically while the window was inactive.
In sticking with the norm on GNOME, Firefox should probably fire focus events for controls after all window:activate events. If not, an AT will have to predict whether a window:activate will be followed by a focus: or not, and decide whether to use its own cached focus point of regard or wait for the focus event to occur.
Assignee | ||
Updated•18 years ago
|
Assignee | ||
Comment 1•18 years ago
|
||
Is this a dupe of bug 368322 ?
Marking as dupe of newer bug which has more info.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•