Use category flush for focus events.
At times, we receive multiple focus events. This is technically fine, but it can cause lots of queued up chatter. In the linke to bug, we are reading a focus event from a previous tab. Ideally the focus event shouldn't be fired (as it once was not), but ChromeVox should be robust enough to not over speak in this case. Note that in braille, this results in a "shuffling" effect where one focus event flashes briefly before the expected event comes through. BUG=646126 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2331253002 Cr-Commit-Position: refs/heads/master@{#419240}
Showing
Please register or sign in to comment