| commit | 7f59479d0e8ab664da79227d96ccf79dd3f06d1d | [log] [tgz] |
|---|---|---|
| author | Rupert Ben Wiser <[email protected]> | Fri May 02 08:03:06 2025 |
| committer | Copybara-Service <[email protected]> | Fri May 02 08:10:30 2025 |
| tree | 46d982043ac125c656b62de547de91946627914b | |
| parent | c576e5700f98564654bccf9be9227c8793d58e33 [diff] |
webview: Add boundary interface for builder state configuration Planning to experiment with a builder pattern to create a WebView. Under the hood this will still initially construct a WebView with the framework constructor (could re-think that in the future) but it would give us the opportunity to configure the state that we know wouldn't change and would be configured before WebView is used anywhere. From AndroidX's perspective just gets a configured WebView back. Adding a single configure boundary interface so that we can encode new configurations into this, and not add a cost of adding new interfaces in the future. Build is always going to happen on the UI Thread so each configuration will deal with its own validation. Bug: b:409740828 Change-Id: I73fc218c75d1568eb8d33ee969c058ae736c4fa0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6448551 Reviewed-by: Ashley Newson <[email protected]> Reviewed-by: Peter Pakkenberg <[email protected]> Reviewed-by: Richard (Torne) Coles <[email protected]> Commit-Queue: Rupert Wiser <[email protected]> Cr-Commit-Position: refs/heads/main@{#1454864} NOKEYCHECK=True GitOrigin-RevId: e666811c7198a7f0a4424516173c0f674bfa8c24
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.