Fix the icon loading issue for Chrome apps running in Lacros.

When StandaloneBrowserExtensionApps::OnApps is called, apps are
published to AppRegistryCache, and the OnAppUpdate notifies the shelf to
load icons for apps. However,
StandaloneBrowserExtensionApps::RegisterAppController might not be
called yet to bind the Crosapi controller, so load icon failed for the
shelf. Call sequence:
1) StandaloneBrowserExtensionApps::OnApps
     PublishApps to AppRegistryCache
       Shelf::OnAppUpdate is called
         Shelf calls LoadIcon
2) StandaloneBrowserExtensionApps::LoadIcon {
  if (!controller_.is_bound()) {
    std::move(callback).Run(apps::mojom::IconValue::New());
    return;  // Crosapi is not bound yet, load icon failed.
  }
3) StandaloneBrowserExtensionApps::RegisterAppController is called to
   register Crosapi

This CL modifies StandaloneBrowserExtensionApps::OnApps to check whether
CrosApi is registered, controller is bound. If not, save apps to the
local cache, and when register Crosapi, publish apps in cache.

This CL also modified `should_notify_initialized`. Add a local variable
'should_notify_initialized_' to set the should_notify_initialized as
true when publish apps for the first time. When CrosApi is registered
for the first time, set should_notify_initialized as true if apps
haven't been published yet.

Add tests to verify OnApps, and should_notify_initialized.

Web apps should have the similar issue as well. There will be a follow
up CL to address the issue for web apps running in Lacros.

BUG=1310962

Change-Id: I033df05c19c5dea678bde140873e3e0765707b36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3568007
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Cr-Commit-Position: refs/heads/main@{#988888}
3 files changed
tree: acd9f5db84d41a331f777c7c4856ddd4129d2564
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

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.