chromeos: wires up can-focus
There are a couple of issues addressed here: . kFocusable_InitProperty was not wired up correctly. . Ash created top-levels were not picking up the value set by clients To fix these I'm adding kCanFocus. ws2 sets this from calls by clients to WindowTree::SetCanFocus(). Ash uses this property as well if the client supplies kFocusable_InitProperty. I think kFocusable_InitProperty should go away. That'll be easier once we get rid of --mash. I'm also forking the TopLevelWindowFactory tests. I moved the existing ones into TopLevelWindowFactoryMash (these only run with --mash). I also made the tests work in classic mode with ws2. I added a new file for this that is built in ash_unittests. BUG=842301 TEST=covered by tests Change-Id: I016ed612e7ab1d7bc1cdc4840c3aa9271078ab9e Reviewed-on: https://chromium-review.googlesource.com/1086151 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#564646}
Showing
Please register or sign in to comment