GitLab

Adds browsertest that ensures that on Win a focus event always fires when navigating to another page

If a user of Jaws or NVDA screen reader navigates to another page,
they expect their screen reader focus to move to the web contents, otherwise
they might develop the mistaken belief that the virtual buffer hasn't loaded.
I wasn't able to add a DumpEventTest under content/test/data/accessibility/events
because we filter out all focus events and adding them back would cause too many other tests to fail randomly.
This Windows specific browser is my best shot at testing this expectation.

R=dmazzoni@chromium.org, kbabbitt@microsoft.com

Bug: 1058959
Change-Id: I161ea42c38220d5245b68d271af74f8b748b95ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097389Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#749195}