Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(2171)

Unified Diff: ash/wm/drag_window_controller.cc

Issue 286733002: [Refactor] Consolidate the logic for whether a widget can be activated. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 6 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: ash/wm/drag_window_controller.cc
diff --git a/ash/wm/drag_window_controller.cc b/ash/wm/drag_window_controller.cc
index eee66e46c5ed5db0a10c448b31353b9fd2f85c10..ecd2a5b6a99b21ee5dd3e2ff4171eca23deec56e 100644
--- a/ash/wm/drag_window_controller.cc
+++ b/ash/wm/drag_window_controller.cc
@@ -66,7 +66,7 @@ void DragWindowController::CreateDragWidget(const gfx::Rect& bounds) {
views::Widget::InitParams params(views::Widget::InitParams::TYPE_POPUP);
params.opacity = views::Widget::InitParams::TRANSLUCENT_WINDOW;
params.parent = window_->parent();
- params.can_activate = false;
+ params.activatable = views::Widget::InitParams::ACTIVATABLE_NO;
sky 2014/05/14 14:06:30 How come you're explicit here, but in places like
pkotwicz 2014/05/14 15:24:38 There is no reason to be explicit here (or anywher
params.keep_on_top = true;
drag_widget_->set_focus_on_creation(false);
drag_widget_->Init(params);

Powered by Google App Engine
This is Rietveld 408576698