[BCIV] Add OffsetTag to scroll toolbar hairline without extra frames

The toolbar hairline should instantly disappear/appear when the toolbar is scrolled off/on screen. This is done by hiding/showing the slim::Layers for the composited toolbar, but a compositor frame is sent every time the visibility changes. We don't want these compositor frames to be sent, because it causes jank and increases latency.

In the current state of BCIV, we use one OffsetTag to move everything, meaning that the toolbar and viewport must move together by the same amount. The hairline is below the toolbar and z-indexed on top of the viewport, so if we don't send the compositor frames to hide the composited toolbar, the hairline will stay visible at the top of the screen. We fix this problem by scrolling only the toolbar layer a bit farther, so that the toolbar+hairline is moved completely off the screen without anything else moving incorrectly. This CL introduces another OffsetTag, so that the toolbar and viewport each have their own OffsetTag and can be scrolled with different offsets. This CL also removes the additional compositor frames for hiding/showing the hairline by making the composited toolbar always shown.

Bug: 373705114
Change-Id: If943c877b0c60cd2f15842d01a4f6bca080d4142
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5933670
Reviewed-by: Kyle Charbonneau <kylechar@chromium.org>
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Theresa Sullivan <twellington@chromium.org>
Commit-Queue: Peilin Wang <peilinwang@google.com>
Cr-Commit-Position: refs/heads/main@{#1372804}
17 files changed
tree: c46850fefdd703fd415e876d2f3c1f1ba49dd6b0
  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. google_update/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  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. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. 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.