[views-ax] Migrate kName in TabGroupHeader

This CL migrates the kName attribute in views to be updated
whenever its value should change, rather than querying the value
and computing it only when needed.

The accessible name of a TabGroupHeader depends on the following properties:

1. The title of the TabGroup
2. The collapsed state of the TabGroup
3. The content string of the TabGroup, which is influenced by the title of the first tab and the number of tabs in the group.

Since the accessible name of the TabGroupHeader depends on the title of the
first tab in the group, we track Tab::SetData() whenever it attempts to
update the tab’s title. If an update occurs,
TabGroupHeader::UpdateAccessibleName() is called.

Additionally, whenever a tab is added to or removed from a TabGroup, the
accessible name of the TabGroupHeader must be recalculated. To achieve
this, we need to add a callback in the TabGroup class and execute it
whenever a tab is added or removed.

The tab’s title update request is initially handled in WebContents,
and then a subsequent UI update is scheduled for the browser to handle.
The title update is performed through a delayed task to avoid flickering.

This CL is part of the ViewsAX project:
https://docs.google.com/document/d/1Ku7HOyDsiZem1yaV6ccZ-tz3lO2XR2NEcm8HjR6d-VY/edit#heading=h.ke1u3utej413

Bug: 325137417
Change-Id: I1b9440d4289df7dec3781738d571db0e7deff220
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5922293
Reviewed-by: Jacques Newman <janewman@microsoft.com>
Commit-Queue: Gaurav Kumar <gauravkum@microsoft.com>
Reviewed-by: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1383449}
18 files changed
tree: f439a08772f76503a6733a97afa20192d7cee9b2
  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.