Issue 85354 - Accessibility Workbench should catch TRANSIENT / EventBroadcaster mismatch
Summary: Accessibility Workbench should catch TRANSIENT / EventBroadcaster mismatch
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 680m242
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-01-18 10:08 UTC by nospam4obr
Modified: 2017-05-20 11:33 UTC (History)
3 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description nospam4obr 2008-01-18 10:08:11 UTC
Accessibility implementations should either implement
XAccessibleEventBroadcaster or expose the TRANSIENT state. Even though doing
none of both now gets asserted by the UNO ,-> ATK bridge (see issue 74943),
finding such problems with the AccessibilityWorkbench seems to be a lot easier
(as it also exposes the UNO service name of the failing component).
Comment 1 nospam4obr 2008-01-18 13:47:27 UTC
Accepting issue.
Comment 2 nospam4obr 2008-07-29 07:52:00 UTC
Re-assigned to new maintainer.
Comment 3 ab 2008-08-01 12:07:45 UTC
Comment 4 williewalker 2009-03-24 19:35:57 UTC
Trackback to the Orca bug:
Comment 5 nospam4obr 2009-03-25 10:06:54 UTC
Shouldn't the traceback have gone to issue 74943 ? The Accessibility Workbench
is just a test tool similar to accerciser, at-poke & JavaMonkey. 
Comment 6 malte_timmermann 2009-12-03 10:54:17 UTC
Removed accessibility keyword. This helps for accessibility implementation
testing, but it's not an accessibility issues.

Target OOo Later: If someone actually needs this feature, contact AB on demand.
Comment 7 Marcus 2017-05-20 11:33:42 UTC
Reset assigne to the default "".