GNOME Bugzilla – Bug 758189
Entry completion pop-up items lack "focused" AtkState
Last modified: 2018-02-10 15:59:44 UTC
Created attachment 315698 [details] pyatspi accessible-event listener Steps to reproduce: 1. Launch the attached accessible-event listener in a terminal 2. Launch gtk3-demo's Entry Completion demo 3. Type "t" to cause the completion pop up to appear 4. Arrow Up/Down between the two popped-up items Expected results: Items emitting object:state-changed:focused (true), would have the "focused" AtkState type in its state set. Actual results: Items emitting object:state-changed:focused (true), lack the "focused" AtkState type in its state set.
Sample output from performing the steps in the opening report: object:state-changed:focused True [text | ] object:state-changed:focused False [table cell | total] object:state-changed:focused True [table cell | total] ERROR: Event state (True) does not match object state (False) object:state-changed:focused False [table cell | total] object:state-changed:focused True [table cell | totally] ERROR: Event state (True) does not match object state (False)
well, its not focused - the focus is in the entry
Fair enough. But then perhaps it would make sense to stop emitting object:state-changed:focused events on things which are not focused.
See also bug 758298.
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
*** This bug has been marked as a duplicate of bug 711397 ***