Fix scaling for 9-patch scrollbars.

When pinch-zooming in a subscroller that is being rendered with nine-
patch scrolling the track shows strange behavior. In official builds
the rendering of the thumb and arrows gets distorted and in local
builds it is clear that the scrollbar's track and buttons are not
being scaled.

The root causes for this bug were:
1. The patch generator was not being passed the scaled rect by the layer
   code, it was only being given the layer's dimensions.
2. The track's bitmap wasn't being repainted when scaled, which in the
   best case scenario caused the arrows to look blurry, and in the worst
   it caused the rendering to be completely wrong.
3. The aperture wasn't being scaled to consider the bitmap's scaled
   dimensions, which caused scaled scrollbars to be rendered
   incorrectly.

This CL:
1. Adds a new condition for the scrollbars to be re-painted whenever the
   layer's internal scale changes.
2. Refactors the ScrollbarTheme 9patch-Canvas and 9patch-Aperture code
   to consider the scale of the layer and return the correct sized
   values.
3. Adds web and unittests to cover the new behavior.

Bug: 378027651
Change-Id: Ie467ecc8139e2a6b03d5d073ac2c860bf2cd571d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6013524
Commit-Queue: Gaston Rodriguez <gastonr@microsoft.com>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Yaroslav Shalivskyy <yshalivskyy@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1385971}
37 files changed
tree: 1b511955bf1c0d841e3371a13cbefb00eb2d9627
  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.