Set focusibility correctly when initializing a window in mus+ash.

ui/views/mus/mus_client.cc

Index: ui/views/mus/mus_client.cc
diff --git a/ui/views/mus/mus_client.cc b/ui/views/mus/mus_client.cc
index 2a73231972a333202e7dd245ed9ec78d49577652..e06c27fea7321837f5514dc13edcbb93027c8064 100644
--- a/ui/views/mus/mus_client.cc
+++ b/ui/views/mus/mus_client.cc
@@ -151,6 +151,9 @@ MusClient::ConfigurePropertiesFromParams(
       mojo::ConvertTo<std::vector<uint8_t>>(
           static_cast<int32_t>(init_params.type));
 
+  properties[ui::mojom::WindowManager::kActivatable_InitProperty] =
+      mojo::ConvertTo<std::vector<uint8_t>>(init_params.CanActivate());

[sadrul, 2017/01/24 17:34:49]

Instead of introducing a property for this, can mus-client just use the
WindowTree::SetCanFocus() API?

[Hadi, 2017/01/24 18:42:33]

WindowTree::SetCanFocus() needs window_id, but I think we don't have it here
yet. Am I missing something?

[sadrul, 2017/01/25 05:31:40]

The window-id is set pretty early on in the client-side during initialization
[1]. If we notify the server SetCanFocus() right after calling
NewTopLevelWindow() [2], would that work?

1:
https://cs.chromium.org/chromium/src/ui/aura/mus/window_tree_client.cc?type=c...

2:
https://cs.chromium.org/chromium/src/ui/aura/mus/window_tree_client.cc?type=c...

+
   if (!init_params.bounds.IsEmpty()) {
     properties[ui::mojom::WindowManager::kBounds_InitProperty] =
         mojo::ConvertTo<std::vector<uint8_t>>(init_params.bounds);