commit | e0694def60e89d445d7730df4ac9f2b968032b18 | [log] [tgz] |
---|---|---|
author | Daniel Murphy <dmurph@google.com> | Mon Oct 24 20:03:26 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 24 20:03:26 2022 |
tree | 282c4266d0cb5cc2d1f5c696499d745448b821f2 | |
parent | 31ec2ef92bdd9419cd1301689c2203610e44f910 [diff] |
[dPWA] Refactoring launches to always be async. Context: Reading information from the WebAppProvider system is often inherently racy (given all of our async data sources). Putting operations behind commands guarantees the the data read is not going to change across async calls (and that you aren't reading it in the middle of an operation like 'install', 'uninstall', etc). This project protects 'launch' to make sure it doesn't happen during an 'uncommitted read' state. This change was created by using 'git cl split', and is the first part in making dPWA launches async. The app service is designed to have launches be async (and in lacros they will ALWAYS be async), but currently they are "mostly" synchronous. This means that there are a variety of tests (and even one instance of production code - the intent launcher) which assumes this. This patch fixes all of those cases. Specifically patches split here: * Add browser or navigation waiters to wait until launches complete in tests. * Modifies the method signatures required for making launches async for making launches async (but just calls the callback synchronously for now. * Fixes a future bug for Lacros where the intent navigation closes the window before launching the app, causing the browser/profile to start shutting down. Keep-alives were added to ensure this does not happen. There is no functional change in this patch. If you want to see a patch with all test changes & functionality changes, see: https://chromium-review.googlesource.com/c/chromium/src/+/3929017 $description This CL was uploaded by git cl split. R=tobyhuang@chromium.org Bug: b/242059352, 1377102 Change-Id: Ifffb6083d65c69de119475c7720779e579581481 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3969023 Reviewed-by: Toby Huang <tobyhuang@chromium.org> Auto-Submit: Daniel Murphy <dmurph@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/main@{#1062966}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.