UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3500.0 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome/Chromium
  * export ACCESSIBILITY_ENABLED=1, and
  * launch with --force-renderer-accessibility

2. Launch the attached accessible-event listener in a terminal

3. Change the active window between Chrome/Chromium and other accessible apps

What is the expected behavior?
The event listener would print out events each time Chrome/Chromium became the active window.

What went wrong?
The event listener does not print out any events.

Did this work before? No 

Chrome version: 70.0.3500.0  Channel: n/a
OS Version: 
Flash Version: 

Compare to: Firefox (with accessibility enabled), Epiphany, any Gtk+ app

Documentation: https://developer.gnome.org/atk/stable/AtkWindow.html, https://developer.gnome.org/atk/stable/AtkObject.html#AtkObject-state-change

Impact: Orca receives no notification when the user launches or switches back to Chrome/Chromium. Orca uses these notifications not only to present the newly-activated window to the user, but also to load the appropriate application and/or toolkit script, update state, filter out events from non-active apps, etc.
 

Deleted: window-activate-events.py 464 bytes

window-activate-events.py 464 bytes View Download