Closed
Bug 154721
Opened 22 years ago
Closed 22 years ago
Active Accessibility: focus events not working on documents
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
Attachments
(1 file)
When a document is focused, GetFocusedElement() returns null, and thus GetAccFocused() cannot create an accessible. I have a patch forthcoming that changed GetFocusedElement() to GetFocusedNode(), which will return the document node when the document is focused. This fixes the situations.
Assignee | ||
Comment 1•22 years ago
|
||
seeking r=
Comment on attachment 89490 [details] [diff] [review] Changes GetFocusedElement() to GetFocusedNode(), which can now see document dom node focus. Also changes Accessible.cpp so that it fires focus events again. r=kyle Yes, GetFocusedNode is more reasonable.
Attachment #89490 -
Flags: review+
Comment 3•22 years ago
|
||
Comment on attachment 89490 [details] [diff] [review] Changes GetFocusedElement() to GetFocusedNode(), which can now see document dom node focus. Also changes Accessible.cpp so that it fires focus events again. + /* + // Remove this until we can figure out which focus events are coming at + // the same time as native window focus events, although + // perhaps 2 duplicate focus events on the window isn't really a problem ... + */ Please use #if 0 ... #endif to take out blocks of code, using comments is error prone... sr=jst
Attachment #89490 -
Flags: superreview+
Assignee | ||
Comment 4•22 years ago
|
||
checked in a while back.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•