Closed Bug 529816 Opened 16 years ago Closed 15 years ago

nsAccessibilityService::GetAccessible should take an nsWeakFrame instead of nsIFrame

Categories

(Core :: Disability Access APIs, defect)

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

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: davidb, Assigned: davidb)

Details

Let's do this after 3.6 ships. (Spin off from bug529442 comment 6)
after 3.6 ships we should try to move *aFrameHint logic into nsAccTreeWalker.
Can you explain what "*aFrameHint logic" is? Do you mean the contents of nsAccessibilityService::GetAccessible?
(In reply to comment #2) > Can you explain what "*aFrameHint logic" is? Do you mean the contents of > nsAccessibilityService::GetAccessible? Yes, we should remove aFrameHint argument from GetAccessible, and drive frames inside of nsAccTreeWalker. Ideally. This argument is used by nsAccTreeWalker, so it's in bad place.
No longer needed.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.