GNOME Bugzilla – Bug 616693
Cause expanding/collapsing a combo box to emit object:state-changed:showing
Last modified: 2015-02-27 16:56:48 UTC
Compare the following events from collapsing a combo box from both the SwingSet2 demo and gtk-demo: object:state-changed:visible(0, 0, None) source: [popup menu | ] application: [application | SwingSet2] ================================================ object:state-changed:showing(0, 0, None) source: [menu | ] application: [application | gtk-demo] object:state-changed:visible(0, 0, None) source: [menu | ] application: [application | gtk-demo] I have the Severity as 'enhancement' because the main issue for Orca in this regard is that, in general, we get tons of events. We try to avoid registering for what seems like redundant events because it's just more stuff to process that we don't need. We aren't registering for object:state-changed:visible because it always seems to come with object:state-changed:showing which we do register for. What would be really, really nice from the Orca perspective is if the Java Atk Wrapper could emit both the visible and showing events. If this isn't doable, Orca can cope with what we are getting. Thanks!
Joanmarie, I try to monitor the event for gtk-demo. Seemed visible and showing events won't emit together sometime, especially for windows(I enclosed one events log in attachment. Do you still prefer Java ATK Wrapper emit visible and showing both on all objects like this: object:state-changed:showing(0, 0, None) source: [popup menu | ] application: [application | SwingSet2] object:state-changed:visible(0, 0, None) source: [popup menu | ] application: [application | SwingSet2] and object:state-changed:visible(1, 0, None) source: [popup menu | ] application: [application | SwingSet2] object:state-changed:showing(1, 0, None) source: [popup menu | ] application: [application | SwingSet2] I am not sure if it will bring any side effection current.
Created attachment 187613 [details] event log file Here is that event log file
Created attachment 188359 [details] [review] patch to fix this issue
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports. IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Review of attachment 188359 [details] [review]: It's been such a while since this patch was made that it no longer applies, unfortunately. Are you able to make a master compatible version for testing?
Review of attachment 188359 [details] [review]: On checking this again I see that this patch was actually already committed with https://git.gnome.org/browse/java-atk-wrapper/commit/wrapper/org/GNOME/Accessibility/AtkWrapper.java.in?id=5b0b399d0b7c7c6f8936d7fe3fcddc2de58c2972 and just not marked. I will close this.
[Moving at-spi/java-atk-wrapper bugs to separate product. See bug 740075]