Code inclusion: add setSafeBrowsingAllowlist boundary interface

This adds setSafeBrowsingAllowlist (behind the DEV_SUFFIX) and
deprecates the setSafeBrowsingWhitelist boundary interface. These are
functionally similar, although setSafeBrowsingAllowlist accepts a
Set<String> since this is a more appropriate data type.

This adds an UMA counter for the new API and adds missing enum labels
for other APIs.

This CL also renames a couple references to the old API to be
SET_SAFE_BROWSING_ALLOWLIST_DEPRECATED_NAME instead, to minimize
non-inclusive terminology.

Fixed: 1108667
Test: N/A
Change-Id: I49ef11e4346e631e14b822943abb6482837d60a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321523
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Laís Minchillo <laisminchillo@chromium.org>
Reviewed-by: Laís Minchillo <laisminchillo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792830}
GitOrigin-RevId: 58274f4e7182ab76f09f247a55846fc2bf5f8b3f
2 files changed
tree: 0b80a36c9904eb1df7508ba11a729cf9fcf54d0c
  1. .gitignore
  2. BUILD.gn
  3. DEPS
  4. OWNERS
  5. README.md
  6. proguard.flags
  7. src/
README.md

Webkit Boundary Interfaces

Note: the canonical copy of the boundary interfaces lives in the chromium repository; this subdirectory of chromium is mirrored into the Android project for use by the webkit AndroidX module.

If you‘re reading this file in the Android repository, don’t make changes in this folder. Please make changes in chromium, or contact the OWNERS in frameworks/support/webkit/.

If you're reading this file in the chromium repository, you should feel free to make changes. Please be aware that this folder has strict import requirements (enforced by DEPS), because it must continue to build when mirrored into Android.