cros_next: make switch inherit from ToggleButton

Previously, we built the KnobSwitch class from scratch. However
the existing ToggleButton has similar functionalities and also
implements the animation, hover layer, ink drop layer and
animation. To avoid re-invent the wheel, we decide to make
KnobSwitch inherit from ToggleButton. This cl makes following
changes:

The changes in ui/views/controls/button/toggle_button.*:
- Change the type of thumb on/off colors and track on/off
colors from absl::optional to
absl::variant<ui::ColorId, SkColor> such that they can hold
both color ID and color value.
- Update the enabled/disabled colors when the enabled state
of ToggleButton is changed.
- Add a new has_thumb_shadow_ attribute in ToggleButton such
that the sub classes can specify if they want a thumb shadow.
- Add a new has_shadow_ attribute in ThumbView to receive the
value of has_thumb_shadow_ from ToggleButton.
- Make GetFocusRingPath, GetTrackBounds and GetThumbBounds as
virtual protected methods such the the sub classes can override
them.
- Add a protected method GetAnimationProgress for sub classes
to get the value from slide animation.

The changes in ash/style/ash_color_mixer
- Change the toggle button related colors with dynamic color Id
in ash color mixers.

The changes in ash/style/knob_switch.*
- Change the name from KnobSwitch to Switch because many people
feel the name knob switch is confusing.
- Inherit the Switch from ToggleButton and override the
GetFocusRingPath, GetTrackBounds, and GetThumbBounds.

The final effects will be shown in bug comment.

Bug: b:271330235
Change-Id: I7051484ea80656ce97cc837fef79641a4b1708ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4338876
Reviewed-by: Sean Kau <skau@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Xiaodan Zhu <zxdan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118466}
13 files changed
tree: 5b871f42460fa17617fa7ab4cfbcc67f3359a98e
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  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. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.