This manifests most noticeably in:
- naviagte quickly in a site like blindcooltech by heading
- notice if you do it quickly enough, focus events come in *after* we've already announce the current range
We need some way to distinguish between user initiated events and focus events sent by the web page.
In Classic, since everything was sync, we were able to simply ignore events while we were in the event loop for a key event.
In Next, it would be great to get an event for user initiated focus (or a flag).
Comment 1 by lpalmaro@chromium.org
, Sep 20 2016