[ntp modules] Decouple load/reload logic (bug fix).

`loadModules()` loads the NTP modules container. Currently, it is
callable on initial load[1] and during reload[2] (if no modules shown
and module reload behavior is feature enabled), leading to potential
conflicts.

This change
1. Makes `loadModules()` only callable during initial load. Modules
enabled during this initial load will wait for it to finish before being
loaded into the container.
2. Restricts reload logic, so that it can only be triggered after
`loadModules()` has started loading modules. Otherwise, we can assume
that `loadModules()` will be called at some point in the future, and
that we don't need to reload anything yet.
3. Checks for an existing template instance right before creating a new
one. This prevents race conditions where another part of the code might have added the instance in the meantime.

[1]https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/resources/new_tab_page/modules/v2/modules.ts;drc=3e99cfbf333b0e33b0f656682260b6b78f6368ff;l=301
[2]https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/resources/new_tab_page/modules/v2/modules.ts;drc=3e99cfbf333b0e33b0f656682260b6b78f6368ff;l=333

Change-Id: Ifc3cf09ac258c5d8312cda9372149c8a6c1ad19e
Bug: 394335176
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6231292
Reviewed-by: Riley Tatum <rtatum@google.com>
Commit-Queue: Paul Adedeji <pauladedeji@google.com>
Cr-Commit-Position: refs/heads/main@{#1416480}
2 files changed
tree: c3aecd8aeca96e8c43f41b76eb6e3435ce5191d7
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.