521730 - bullet accessible should be created based on nsBulletFrame

Status: RESOLVED WORKSFORME

(Core :: Disability Access APIs, defect)

Description

[alexander :surkov (:asurkov)]

nsAccessibleTreeWalker can't create bullet accessible by its frame (nsBulltetAccessible) and html:li accessible has special code to create bullet accessible which should be fixed.

spun off the bug 496783

Comment 1

[alexander :surkov (:asurkov)]

bounds and getChildAtPoint is wrong for bullet accessibles as well, I hope switching to bullet frame usage helps with this as well

Comment 2

[alexander :surkov (:asurkov)]

Attachment: unsuccessful wip

nsAccTreeWalker doesn't see bullet frame because it doesn't walk by frames and bullet frame shares content with list item. So neither DOM nodes traverse nor anonymous content creator work here. Since bullet frame doesn't have own content we can't get rid special handling of bullet accessible in html list item accessible: we need to keep pointer on it and destroy when list item accessible is destroyed. I think there is no win until bullet frame has content and it is discoverable by more or less general way (for example, via anonymous content creator).

Comment 3

[alexander :surkov (:asurkov)]

(In reply to comment #2)

> I think there is no win until bullet frame has content
> and it is discoverable by more or less general way (for example, via anonymous
> content creator).

It is because bounds and hit test will be fixed.

Comment 4

[alexander :surkov (:asurkov)]

It might be implementing GetFrame() method on nsHTMLListBulletAccessible will fix boundary and childAtPoint problems.

Comment 5

[alexander :surkov (:asurkov)]

afaik hit test and boundaries for bullets were fixed, I don't think we need this bug anymore