Correct a few assumptions in Android Webview code around fenced frames.

- Ensure the frame is the outermost main frame when directing
navigations to the webview code.
- Ensure DocumentHasImage is called only from the outermost main frame.

BUG=1314858

Change-Id: I69cdf6a803f7066603a8c9e631f4213195d3a9e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3631235
Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001169}
NOKEYCHECK=True
GitOrigin-RevId: 436e32b899726d91179ee6604896990bad35b417
1 file changed
tree: b47b7ddf6fd4f8b002a4fd6fcb05940a405630e5
  1. java/
  2. BUILD.gn
  3. README.md
README.md

//android_webview/glue/

This folder contains a shim layer between the public frameworks APIs (android.webkit.*) and WebView's implementation, and allows them to (mostly) not directly depend on each other.

Folder Dependencies

//android_webview/java/ must not depend on this directory.

See Also