commit | bca90a8a2b5d2e9c3acf2a8a31653e3049448572 | [log] [tgz] |
---|---|---|
author | Boris Sazonov <bsazonov@chromium.org> | Fri May 24 14:15:26 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 24 14:15:26 2024 |
tree | f3b343bb50765cd4cab309cd0f5c50a0859949ee | |
parent | 84b47f843c89a6f958eb46dd23d8fa8d37d9ab03 [diff] |
Reland "[UNOp2][Android] Make account info acquisition as synchronous as possible" This is a reland of commit d2bae94e74f98733f696afb04cd31e2237d5d17a Test issues that caused the revert were fixed by https://crrev.com/c/5563689. Original change's description: > [UNOp2][Android] Make account info acquisition as synchronous as possible > > ProfileDataCache extensively uses Promise while populating account > info. Since fulfilled promises still post a task to the UI thread that > is executed on the next frame - the profile data won't be available > until those tasks are executed (this was taking up to 3 frames prior to > this CL). This CL addresses the issue by adding some explicit checks > for whether the promise is already fulfilled. This is a temporary > solution that will be simplified after https://crbug.com/341948846 is > addressed. > > Bug: 330357665 > Change-Id: Ie4ce868555e2760fd59ef47755149b80c1c0ff10 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5547669 > Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> > Reviewed-by: Menghan Yang <myuu@google.com> > Commit-Queue: Boris Sazonov <bsazonov@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1304940} Bug: 330357665, 342370154 Change-Id: I133200be907a98d0657cd6a2b67704ad0ef081fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5569251 Reviewed-by: Menghan Yang <myuu@google.com> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/main@{#1305688}
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.