[M144] Update zoom page action properties before bubble visibility

Original change's description:
> Update zoom page action properties before bubble visibility
> 
> Extract the logic for updating the zoom page action's accessible name,
> tooltip, and image into a separate method,
> `UpdatePageActionIconProperties`. This new method is invoked prior to
> `UpdateBubbleVisibility`. The logic to show or hide the page action icon
> remains in `UpdatePageActionIcon` and is executed afterwards.
> 
> Root cause:
> In the current flow, showing / refreshing the zoom bubble can synchronously trigger reads of the anchor’s accessible name / tooltip (and may also trigger an A11y announcement) as part of the bubble update. If we update the page action properties after calling Show() / RefreshIfShowing(), then:
> 
> the bubble refresh path can pull the old accessible name/tooltip (X%) during its construction/refresh, and/or
> 
> an A11y event/announcement can fire immediately using whatever name is set at that instant (still X%),
> 
> and only after that we override the accessible name/tooltip to Y%. At that point it’s “fresh” for subsequent reads, but the announcement/UI work already happened.
> 
> Fix:
> This sequence guarantees that the zoom page action icon reflects the
> updated zoom percentage and correct icon state before the zoom bubble is
> updated or shown.
> 
> Recording: https://screencast.googleplex.com/cast/NjI3MzEzNTYzOTc4OTU2OHwzZDhmM2Y1NC0yMA
> 
> Bug: 481634944
> Change-Id: Ice8eb4c12e902d63aa3efae9fc900cb08c217da4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7573545
> Reviewed-by: Kaan Alsan <alsan@chromium.org>
> Commit-Queue: Daniel Soromou <koretadaniel@chromium.org>
> Reviewed-by: Darryl James <dljames@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1584825}

(cherry picked from commit 4f366c116a614241606c85b7156c33a91ed1cd0f)

Bug: 485187423,481634944
Change-Id: Ice8eb4c12e902d63aa3efae9fc900cb08c217da4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7595542
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/7559@{#4737}
Cr-Branched-From: 223dfbac1c7542a06b422390d954afe5b560b607-refs/heads/main@{#1552494}
4 files changed
tree: 39a52190fda747a966ab911248103b07045b3b76
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .geminiignore
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. SECURITY_OWNERS
  82. 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.