Closed
      
        Bug 354121
      
      
        Opened 19 years ago
          Closed 13 years ago
      
        
    
  
getFocusedChild() doesn't really (always) get a child  
    Categories
(Core :: Disability Access APIs, defect)
        Core
          
        
        
      
        
    
        Disability Access APIs
          
        
        
      
        
    Tracking
()
        RESOLVED
        WORKSFORME
        
    
  
People
(Reporter: hwaara, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: access, Whiteboard: [bk1])
getFocusedChild() sounds like it would give a child that is focused, and null if none of its children are focused. 
However, it just asks the accessibility service to return whichever accessible that is focused (globally). This can be misleading.
| Comment 1•19 years ago
           | ||
Actually for tree it returns the focused descendant.
We can change it so that the returned accessible is set to null if it's not a decsendant, and change the name to getFocousedDescendant.
Keywords: access
|   | Reporter | |
| Comment 2•19 years ago
           | ||
Aaron, could getFocusedDescendant use the caret accessible to quickly fetch the focused element (and then see if it's a descendant)?
|   | Reporter | |
| Comment 3•19 years ago
           | ||
Actually, I think getFocusedElement() would be enough for my uses. This could live on nsIAccessibleDocument
If that's what getFocusedChild() does anyway, we could just move it to the root accessible, and the implementation would make sense.
|   | ||
| Comment 5•13 years ago
           | ||
I don't think this is a bug anymore.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
| Comment 7•13 years ago
           | ||
(In reply to David Bolter [:davidb] from comment #6)
> I don't think this is a bug anymore.
FocusedChild() returns a child always for generic accessible, document accessible may return everything but it appears it's by design. Agree on the bug closing but we should provide a reason why the bug is not valid anymore.
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•