Open joanmarie opened 2 months ago
This appears to be fixed by https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7239. Let's hope that lands and lands soon!
@joanmarie I just tested GTK 3.24.42, and it indeed has the initial object:state-changed:focused
in place of the focus:
one :tada:
However, it seems to duplicate several object:state-changed:focused
: basically, whenever you had both object:state-changed:focused
and focus:
, you seem to get object:state-changed:focused
twice. Not sure if it's an issue, but it could possibly be improved.
While technically duplicate events should not be fired, Orca should already be handling that. How it handles it depends on the version of Orca (I've done a lot of work on identifying redundant events as efficiently as possible). So unless Orca is double speaking things, not firing the redundant event seems like a nice-to-have.
Steps to reproduce -- note the order matters.
Expected results: An
object:state-changed:focused
accessibility event would be printed in the terminal.Actual results: Only a
focus:
accessibility event is printed in the terminal.Sample annotated output from icon view:
Sample annotated output from list view:
Notes:
focus:
accessibility event was deprecated over 10 years ago. As a result, I (the maintainer of Orca) have recently removed the handlers from Orca's main branch.@cwendling: Could you please take a look at this one when you have a spare moment? Thanks!