Keyboard input is broken in content_shell
Reported by
j...@jakeonthenet.com,
Jul 19 2016
|
||||||
Issue descriptionChrome Version : git master URLs (if applicable) : google.com Other browsers tested: none What steps will reproduce the problem? (1) build a stock content_shell (2) navigate to google.com (3) try typing in to the search box. nothing appears Note though that the tab key does work - pressing it will move through the focusable elements on the page. What is the expected result? Keys entered should appear in the search box. What happens instead? Keys aren't entered in the search box.
,
Jul 19 2016
The issue seems to be that IME is not receiving the events from aura, which means no keyboard input. content_shell probably needs something like ash/ime/input_method_event_handler to make sure key events are sent to the IME.
,
Jul 20 2016
CL in review: https://codereview.chromium.org/2166863002/
,
Jul 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e0a5b1e243a15dd9d6974953b41000e7131dda8d commit e0a5b1e243a15dd9d6974953b41000e7131dda8d Author: sadrul <sadrul@chromium.org> Date: Thu Jul 21 01:36:46 2016 aura: Fix IME interaction in content-shell in chromeos build. Make sure the key events received by the aura::WindowTreeHost instance goes through the IME, so that text input works correctly. BUG= 629596 Review-Url: https://codereview.chromium.org/2166863002 Cr-Commit-Position: refs/heads/master@{#406740} [modify] https://crrev.com/e0a5b1e243a15dd9d6974953b41000e7131dda8d/ui/aura/BUILD.gn [modify] https://crrev.com/e0a5b1e243a15dd9d6974953b41000e7131dda8d/ui/aura/aura.gyp [add] https://crrev.com/e0a5b1e243a15dd9d6974953b41000e7131dda8d/ui/aura/test/input_method_glue.cc [add] https://crrev.com/e0a5b1e243a15dd9d6974953b41000e7131dda8d/ui/aura/test/input_method_glue.h [modify] https://crrev.com/e0a5b1e243a15dd9d6974953b41000e7131dda8d/ui/wm/test/wm_test_helper.cc [modify] https://crrev.com/e0a5b1e243a15dd9d6974953b41000e7131dda8d/ui/wm/test/wm_test_helper.h
,
Jul 25 2016
I believe that fixes the issue. Closing.
,
Oct 21 2016
Can you provide some verification steps for this bug please?
,
Jan 24 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dpranke@chromium.org
, Jul 19 2016Components: Content>Core
Labels: -Pri-3 Pri-2