Closed Bug 368322 Opened 18 years ago Closed 17 years ago

Missing focus event on chrome when window activated

Categories

(Core :: Disability Access APIs, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: parente, Assigned: aaronlev)

References

(Blocks 1 open bug)

Details

Firefox used to fire a focus event for the chrome object that used to have focus when a Firefox window is restored, activated for the first time, or re-activated. Now, no focus event is fired. A focus event *is* fired if some control in a document last had focus (e.g. document focus followed by link focus), but not if a chrome object had focus (e.g. address bar).

Could someone please spec out what the actual sequence of focus events should be when either a chrome or document accessible has focus and one of the following occurs:

1) The FF window is activated for the first time
2) The FF window is re-activated
3) The FF window is restored
4) An entire document reloads
5) A menu floater is activated (e.g. menu bar menu, popup menu)
6) A tooltip is displayed

It's getting really hard to tell what's a regression and what is an intended change. Please document so we can report bugs appropriately and have a solid plan of how to script Firefox in LSR.
Blocks: keya11y
Dupe of bug 349709?
Blocks: lsr
Is this still a bug in the 4/10 bug? We just fixed a bunch of focus bugs at once.
Peter Parente says this is fixed from one of our recent focus bug fixes.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.