Tweaks to ToggleButton details.

ui/views/controls/button/toggle_button.h

Index: ui/views/controls/button/toggle_button.h
diff --git a/ui/views/controls/button/toggle_button.h b/ui/views/controls/button/toggle_button.h
index 2780b9f8af6da59ac7023249d3d99caffd4d574f..017f8793186b68bfebafd7daad438bb8795a53cc 100644
--- a/ui/views/controls/button/toggle_button.h
+++ b/ui/views/controls/button/toggle_button.h
@@ -49,9 +49,11 @@ class VIEWS_EXPORT ToggleButton : public CustomButton {
   // gfx::AnimationDelegate:
   void AnimationProgressed(const gfx::Animation* animation) override;
 
+  SkColor GetTrackColor(bool is_on) const;

[varkha, 2016/10/21 00:35:18]

nit: I think the style guide asked for the overrides to be after local methods.

[Evan Stade, 2016/10/21 17:19:15]

I don't think it specifies[1] and I believe (without substantiation) it's more
common in Chrome to put overrides first.

[1] https://google.github.io/styleguide/cppguide.html#Declaration_Order

[varkha, 2016/10/21 17:55:36]

No strong opinion here. Just needs to be consistent with the rest of order
(which I have changed because I had this suggested in my CL -
https://codereview.chromium.org/2396133005/diff/80001/ui/views/controls/butto...).

[sadrul, 2016/10/24 14:46:12]

In ui code, I think we fairly consistently put non-overrides before overrides.

+
   bool is_on_;
   gfx::SlideAnimation slide_animation_;
-  std::unique_ptr<ThumbView> thumb_view_;
+  ThumbView* thumb_view_;
 
   DISALLOW_COPY_AND_ASSIGN(ToggleButton);
 };