| commit | d91cda7fa2eeca1e4f2940b050e2c79bf47290be | [log] [tgz] |
|---|---|---|
| author | Chidera Olibie <[email protected]> | Mon Jan 05 17:08:13 2026 |
| committer | Copybara-Service <[email protected]> | Mon Jan 05 17:13:27 2026 |
| tree | 6de963d45f07b6dd9b3af6384ce586c5a6703393 | |
| parent | 02f7bafe04de00fa154ce34ed9fbee6920845903 [diff] |
[wv] Ensure chromium started before accessing ProfileStore I couldn't directly kickstart chromium startup within ProfileStore.getInstance because chromium startup calls into ProfileStore. Other approaches included starting Chromium in `SupportLibWebViewChromiumFactory#getProfileStore` method or create a getProfileStoreInternal() that doesn't initialize awInit. I decided it's better and in align with our current architecture to treat ProfileStore as a ChromiumStartedGlobal because it fits the definition. This builds on pre-existing architecture and prevents new code from accessing ProfileStore before awInit is completed. Bug: 397434566 Change-Id: I2601ca5f1fd258f603bab850a4f7ba42f7a6151c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7392429 Reviewed-by: Richard (Torne) Coles <[email protected]> Commit-Queue: Chidera Olibie <[email protected]> Reviewed-by: Michael van Ouwerkerk <[email protected]> Reviewed-by: Mikhail Khokhlov <[email protected]> Cr-Commit-Position: refs/heads/main@{#1564418} NOKEYCHECK=True GitOrigin-RevId: 5f55ccfa6268de3dfed7f8d582fc2f4f0901328f
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.
//android_webview/java/ must not depend on this directory.