Closed Bug 376803 Opened 17 years ago Closed 13 years ago

Correct logic to determine if nsDocAccessible is focusable

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla10

People

(Reporter: aaronlev, Assigned: surkov)

References

(Blocks 1 open bug)

Details

(Keywords: access) 

Right now in nsDocAccessible::GetState() we have a hack to determine if a document is focusable. We consider all HTML docs focusable and all XUL docs unfocusable.

We need a better way. A XUL <iframe> could contain a scrollable XUL document, which should be focusable (we better make sure it is!) I was not able to find a way to use frame->IsFocusable() to find out if a doc is focusable.
Also, this is a follow-up from bug 375747. The new focusable check for nsDocAccessible comes from that fix.
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Editable frames should be focusable too, presumably.
Blocks: statea11y
Depends on: 673958
Flags: in-testsuite?
fixed by bug 673958
Assignee: nobody → surkov.alexander
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: in-testsuite? → in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
Verified fixed and by inspecting the mochitests from bug 673958 in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a1) Gecko/20110929 Firefox/10.0a1.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.