Index: chrome/browser/ui/views/autofill/autofill_dialog_views.h |
diff --git a/chrome/browser/ui/views/autofill/autofill_dialog_views.h b/chrome/browser/ui/views/autofill/autofill_dialog_views.h |
index 634ca66330626f2003f0ff2b3cffa58515c6709c..86347bbab2dfd6cb24d35e8c5bedf2380232cab4 100644 |
--- a/chrome/browser/ui/views/autofill/autofill_dialog_views.h |
+++ b/chrome/browser/ui/views/autofill/autofill_dialog_views.h |
@@ -250,6 +250,10 @@ class AutofillDialogViews : public AutofillDialogView, |
// when showing the menu or hovered by the mouse cursor). |
void SetActive(bool active); |
Dan Beam
2013/03/26 18:03:14
^ this is why
|
+ // Whether this section can be actively styled or not. If |can_activate| is |
+ // false and this view is currently active, it's deactivated. |
+ void SetCanActivate(bool can_activate); |
ahutter
2013/03/26 15:27:09
Why not style instead of activate? All your commen
Dan Beam
2013/03/26 18:03:14
While I agree and think that Activate is also a vi
|
+ |
// Sets whether mouse events should be forwarded to |proxy_button_|. |
void SetForwardMouseEvents(bool forward); |
@@ -260,6 +264,8 @@ class AutofillDialogViews : public AutofillDialogView, |
virtual bool OnMousePressed(const ui::MouseEvent& event) OVERRIDE; |
virtual void OnMouseReleased(const ui::MouseEvent& event) OVERRIDE; |
+ bool can_activate() const { return can_activate_; } |
+ |
private: |
// Converts |event| to one suitable for |proxy_button_|. |
static ui::MouseEvent ProxyEvent(const ui::MouseEvent& event); |
@@ -267,6 +273,9 @@ class AutofillDialogViews : public AutofillDialogView, |
// Mouse events on |this| are sent to this button. |
views::Button* proxy_button_; // Weak reference. |
+ // When true, this section container can be actively styled. |
+ bool can_activate_; |
+ |
// When true, mouse events will be forwarded to |proxy_button_|. |
bool forward_mouse_events_; |