commit be11a302db1cc8c5fc1cb07c9b939350aa73a9e1
author Jacques Newman <janewman@microsoft.com> Sat Jun 03 01:45:55 2023
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Sat Jun 03 01:45:55 2023
tree 67e5bc80a72fcf9bcfc0c1378112464c6066c738
parent d305f0dcedb7af4a49762e7b6ef9cbec292079ef

Keep sending honey pot messages until we turn on web contents.

This is a high priority change, the bug this fixes is stopping
all JAWS 2021 users from being able to access web contents.

With some Windows 11 features causing kNativeAPIs to be
turned on after startup, our honeypot code was no longer
being triggered. Since there are many other ways to turn
on accessibility this was not noticed until recently.
This change updates our logic to no longer consider the
fact that some accessibility has been enabled as an
indication that we no longer should fire the honey pot
event.

With this change we will continue to send honey pot events
until web contents accessibility has been turned on. The
honey pot will trigger web contents accessibility, and at
that point will no longer fire.

Bug: 1450993
Change-Id: I65cfa0e2c5daf2eaef19241e70e1f23670714216
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4585299
Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1152873}