Open
Bug 644103
Opened 14 years ago
Updated 2 years ago
[meta] smart events filtering depending on event consumer
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: surkov, Unassigned)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
(Keywords: access, meta)
Provide internal interface that allows to skip events coalesce and events collecting when there's no event consumer.
1) XPCOM part
Now we fire or do not fire events depending on whether somebody uses observer service to handle events or not.
First step: move this check to filter events early.
Next step: provide interface to tune this like:
interface nsIAccessibleRetrieval : public nsISupports
{
void addEventHandler(in unsigned long aEventType,
in nsIAccessibleEventHandler aHandler);
void removeEventHandler(in unsigned long aEventType,
in nsIAccessibleEventHandler aHandler);
}
interface nsIAccessibleEventHandler : public nsISupports
{
void handleEvent(in nsIAccessibleEvent aEvent);
}
We could tune it further by moving new methods to document accessible where events processing handled if that's necessary.
2) MSAA/IA2.
Use IsWinEventHookInstalled as Mick suggested in https://lists.linux-foundation.org/pipermail/accessibility-ia2/2010-July/001209.html
3) ATK
Fernando, do you aware how to do that on ATK side?
Reporter | ||
Comment 1•14 years ago
|
||
we need to try to get it in fx5 (at least keep it on radar)
Blocks: a11ynext
Comment 2•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
You need to log in
before you can comment on or make changes to this bug.
Description
•