We expose an accessible for list bullets. Unfortunately, the accessible parent for that is not exposed correctly.
Created attachment 231470 [details] [diff] [review] Use weak reference to enable GetParent() functionality
Attachment #231470 - Flags: superreview?(neil) → superreview+
Attachment #231470 - Flags: review?(ginn.chen) → review+
Whiteboard: Important fix, please see patch for risk assessment, I and reviewers believe it is correct. Has been tested.
Comment on attachment 231470 [details] [diff] [review] Use weak reference to enable GetParent() functionality a=drivers, please land this on the MOZILLA_1_8_BRANCH.
Attachment #231470 - Flags: approval1.8.1? → approval1.8.1+
Is this bullet accessible thing sort of a child node that's not a normal child node? Are there others of that type?
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
There are a few other types: 1. :before and :after text -- although those appear not to be exposed at the moment. That may be a regression but it's not so crucial to deal with for branch IMO. 2. image map areas which are exposed as accessible children of the image rather than of the map 3. Outer doc accessibles own inner doc accessibles. For example an accessible for an <iframe> is the parent of the document accessible within that. 4. HTML select accessibles have a particular structure that mirrors what the DOM would look like for the XBL-based version (e.g. XUL). 5. XUL button accessibles may have 1 child button based on the presence of an anonymous dropdown button (used for the back/forward submenu dropdown buttons on the toolbar) I'm not aware of any issues with any of these items except for the fact that I see #1 is no longer exposed.
You need to log in before you can comment on or make changes to this bug.