Bug 254743

Created attachment 465680 [details] pyatspi accessible-event listener Steps to reproduce: 1. Launch a Gtk3 minibrowser 2. Launch the attached accessible-event listener in a terminal 3. Tab from the URL/location bar down into the content 4. Tab within the content (www.webkitgtk.org) 5. Follow a link from the content (e.g. epiphany) 6. Tab within the newly-loaded content Expected results: Focused-changed events would always be fired and would come from a valid host application Actual results: * On step 3, focus events are emitted as expected: object:state-changed:focused(1, 0, 0) source: [text | ] host_application: [application | MiniBrowser] sender: [application | MiniBrowser] object:state-changed:focused(1, 0, 0) source: [push button | Refresh] host_application: [application | MiniBrowser] sender: [application | MiniBrowser] object:state-changed:focused(1, 0, 0) source: [push button | Find] host_application: [application | MiniBrowser] sender: [application | MiniBrowser] object:state-changed:focused(1, 0, 0) source: [toggle button | Menu] host_application: [application | MiniBrowser] sender: [application | MiniBrowser] * On step 4, no focus events are emitted at all * On step 6, the focus events are emitted, but from a "dead" host application: object:state-changed:focused(1, 0, 0) source: [link | Apps] host_application: [DEAD] sender: [DEAD] object:state-changed:focused(1, 0, 0) source: [link | Web] host_application: [DEAD] sender: [DEAD] object:state-changed:focused(1, 0, 0) source: [link | Home] host_application: [DEAD] sender: [DEAD] object:state-changed:focused(1, 0, 0) source: [link | RecentChanges] host_application: [DEAD] sender: [DEAD] Impact: Orca does not present the focus changes emitted from the document content.