Closed
Bug 282738
Opened 19 years ago
Closed 18 years ago
Expose XTF content in accessibilty tree
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WONTFIX
mozilla1.9alpha8
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
(Keywords: access, Whiteboard: [needed for XForms extension, but not for base Firefox 1.5])
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.
Updated•19 years ago
|
Severity: normal → major
Target Milestone: --- → mozilla1.9beta
Assignee | ||
Comment 1•19 years ago
|
||
Downgrading to normal because XForms does not ship with the browser by default.
Severity: major → normal
Assignee | ||
Updated•19 years ago
|
Whiteboard: [needed for XForms extension, but not for base Firefox 1.5]
Assignee | ||
Comment 2•18 years ago
|
||
Vlad is planning to fix this in a different way.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•