[Toolbar] Remove layoutLocationBar() call from setTabSwitcherMode()

Context: layoutLocationBar() call was added as part of crbug.com/518795 to update the location bar when the tab switcher button is clicked while urlBar expansion is in progress.

This call is now not being invoked in the tab switcher enter flow. We make the tab switcher button not clickable before starting expansion animation [1]. Made the button clickable and slowed down animation to test and the call is still not invoked.

When the tab switcher button is clicked, onUrlFocusChanged(false) is invoked first - we end the running animation here for unfocus [2] and call updateLocationBarLayoutForExpansionAnimation which updates the location bar state for unfocus. Then setTabSwitcherMode() is invoked which calls layoutLocationBar() only when animations are running [3] which is not true anymore.

Intention of removing this call: This method calls updateLocationBarLayoutForExpansionAnimation() which is also called from updateUrlExpansionAnimation(). We want to refactor out updateUrlExpansionAnimation() to a separate class along with updateLocationBarLayoutForExpansionAnimation(). Removing the only other caller helps with this refactor.

[1] https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/android/toolbar/java/src/org/chromium/chrome/browser/toolbar/top/ToolbarPhone.java;l=2058;drc=60130be50f68c89220d8ace62c87155025267a2c?q=Toolbarphone
[2] https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/android/toolbar/java/src/org/chromium/chrome/browser/toolbar/top/ToolbarPhone.java;l=2158-2161;drc=60130be50f68c89220d8ace62c87155025267a2c?q=Toolbarphone
[3] https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/android/toolbar/java/src/org/chromium/chrome/browser/toolbar/top/ToolbarPhone.java;l=1887-1894;drc=60130be50f68c89220d8ace62c87155025267a2c?q=Toolbarphone

Bug: 355074249
Change-Id: Id0dfa6a0cdcc0012839f3118114b8e8a9d5b8cb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5868154
Reviewed-by: Theresa Sullivan <twellington@chromium.org>
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Commit-Queue: Sirisha Kavuluru <skavuluru@google.com>
Cr-Commit-Position: refs/heads/main@{#1383956}
1 file changed
tree: 3091c242688a8a572b035e0985e736f4ede85cd0
  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.