Google Git
Sign in
chromium / chromium / src / 82ac4c81f4643ff3df40d0721d61c04a09c3a830
commit82ac4c81f4643ff3df40d0721d61c04a09c3a830[log] [tgz]
authorVishwas Uppoor <vishwasuppoor@google.com>Thu Dec 12 21:10:21 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Dec 12 21:10:21 2024
tree8506c9b59b235e735e2ef173e0a7fc8bc9a30732
parenta246c769307b0322b957eb8ef07c488bac1b1d0d [diff]
[PIX] Chrome screen visible behind platform screens

After invoking purchase action, the Chrome progress screen persists
behind the platform screens. This is because Chrome isn't informed about
platform screens being shown.

Auto-dismiss the progress screen after a short delay. The delay is
chosen such that the Chrome progress screen is dismissed just after the
platform screen is shown. This gives a smooth transition effect between
different screens.

Before(Chrome progress screen can be seen after the confirmation screen
closes): https://screencast.googleplex.com/cast/NjIzNDQzNDQ2NTQzMTU1MnxmZjdkNzlmNi03OA
After(The progress screen closes slightly after platform screens are
shown): https://screencast.googleplex.com/cast/NTc5NTEwOTY3NjI1MzE4NHwxOTY5MmNjOS02Mw

Fixed: 375678159, 383293247
Change-Id: I0f51660f8745b1eacb695d6ddb6da99fff17ab96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6084819
Reviewed-by: Olivia Saul <jsaul@google.com>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Vishwas Uppoor <vishwasuppoor@google.com>
Cr-Commit-Position: refs/heads/main@{#1395588}
3 files changed
tree: 8506c9b59b235e735e2ef173e0a7fc8bc9a30732
  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. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. 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.