193987 - need ability to fire event in any accObjects

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Kyle Yuan]

Currently, only nsRootAccessible can fire events to nsIAccessibleListener, but
some listeners need to be registered in an individual accObject, for instance,
nsIEditActionListener, so we must be able to fire events from such kind of
accObject.

That's not hard to do - add a handleEvent() into nsIAccessble, each object pass
the call to its parent, till reached the nsRootAccessible.

Comment 1

[Kyle Yuan]

Attachment: patch

also get rid of the unnecessary declaration of AccessibleEventData. the patch
seems long, but most of them is the string replacement.

Comment 2

[Aaron Leventhal]

Kyle, if an object like a textfield is responsible for firing it's own events,
what guarantees that it currently exists?

In other words, if the screen reader releases the leaf object which is
generating events, won't it stop firing them?

Comment 3

[Kyle Yuan]

for the textfield case, I'll call nsIEditor::AddEditActionListener in its
constructor, and RemoveEditActionListener in destructor, that could guarantee
the object won't be released during the event life cycle.
Or, is there any possobility to add such listener in nsRootAccessible? I need
the edit-action-listener because:
1) some dom events do not perfectly match the ATK needs.
2) I'm working on accessibility of Composer that does not fire general events
while typing.

Comment 4

[Aaron Leventhal]

Comment on attachment 114869 [details] [diff] [review]
patch

Okay, you're right.
http://lxr.mozilla.org/seamonkey/source/editor/libeditor/base/nsEditor.cpp#1637
It looks like nsEditor keeps a strong reference to the edit action listeners.

r=aaronl

Comment 5

[Henry Jia]

Comment on attachment 114869 [details] [diff] [review]
patch

sr=Henry

Comment 6

[Kyle Yuan]

checked in!