Expose XTF content in accessibilty tree

RESOLVED WONTFIX

Status

()

Core
Disability Access APIs
RESOLVED WONTFIX
13 years ago
12 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

(Depends on: 1 bug, {access, sec508})

Trunk
mozilla1.9alpha8
x86
All
access, sec508
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [needed for XForms extension, but not for base Firefox 1.5])

(Assignee)

Description

13 years ago
This could be accomplished in one of 2 ways:
1. Handling nsIXTFVisual in nsAccessibleTreeWalker::GetKids() for tree walking,
and nsRootAccessible::GetTargetNode() for finding the final node an event occured on
2. Making XTF mimic XBL so that I can continue to use GetBindingParent() and
GetXBLChildNodesFor(). In that case I just remove the optimization where we
don't check for XBL on HTML nodes.

It would be helpful in any case to have nsIContent::IsContentOfType(eXTF) return
true for these nodes.
(Assignee)

Updated

13 years ago
Depends on: 283257

Updated

13 years ago
Severity: normal → major
Target Milestone: --- → mozilla1.9beta
(Assignee)

Comment 1

13 years ago
Downgrading to normal because XForms does not ship with the browser by default.
Severity: major → normal
(Assignee)

Updated

13 years ago
Whiteboard: [needed for XForms extension, but not for base Firefox 1.5]
(Assignee)

Comment 2

12 years ago
Vlad is planning to fix this in a different way.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.