5f521b98be
WebView needs to decide if we will be drawing this frame at the BeginFrame time, meaning that BeginFrame events needs to flow if there is any undrawn frames. Normally this isn't an issue, because clients actively submitting frames subscribe to them. When client doesn't subscribe to BeginFrames, webviews need to do it when we receive compositor frame that would damage the display. Currently code was using `SurfaceAggregator::previously_contained_surfaces`, which works only after the first frame was embedded. To fix the issue, we use the same code as Chrome that uses `damage_ranges` instead. Bug: 335829864 Change-Id: I2678dc75f70a3c6f2535e318520ef32454762228 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5467023 Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/main@{#1290051}
Android WebView
Android WebView is an Android system component for displaying web content.
WebView (and
the related Android classes) are implemented by the code in the
//android_webview/ folder.
This directory contains the Android WebView implementation, as well as the implementation for the AndroidX Webkit support library.
Overview for Chromium team members and contributors
Please see WebView Architecture.
Want to use WebView in an Android app?
Please consult our API documentation and app development guides:
Want to build and install WebView on a device?
See our Chromium developer documentation.
Public mailing lists
- android-webview-dev@chromium.org: external discussion group for WebView developers and interested community members.
- android-webview-reviews@chromium.org: subscribe to code reviews affecting Android WebView code.