diff options
| author | hbono@chromium.org <hbono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-24 10:05:04 +0000 |
|---|---|---|
| committer | hbono@chromium.org <hbono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-24 10:05:04 +0000 |
| commit | 255184bcbc7f41bccaf11c67dd3f41a79f3950cd (patch) | |
| tree | ce8d441b3828ed3e13ffd943c51dc9221521d78f /DEPS | |
| parent | 65c117758c5acf163331415e6175fcdb85fefde7 (diff) | |
| download | chromium_src-255184bcbc7f41bccaf11c67dd3f41a79f3950cd.zip chromium_src-255184bcbc7f41bccaf11c67dd3f41a79f3950cd.tar.gz chromium_src-255184bcbc7f41bccaf11c67dd3f41a79f3950cd.tar.bz2 | |
A Chrome-side fix for Issue 13233.
To investigate this issue deeply, it seems Flash uses ToUnicode() to verify WM_CHAR events sent from a browser. That is, Flash discards WM_CHAR events if they are different from the characters returned from ToUnicode() calls. So, to fix this issue, we need not only to send WM_CHAR events, but also to synchronize the keyboard layout of a plug-in process with a browser process. To retrieve the keyboard layout of a browser process, this change call GetKeyboardLayout() with the thread id of the parent window. (Even though I'm wondering if this is a good way, I used it since it is not so easy to dispatch the keyboard layout from a browser process to a plug-in process.)
BUG=13233
TEST=LayoutTests/plugins/keyboard-events.html (in my WebKit-side change <https://bugs.webkit.org/show_bug.cgi?id=34936>).
Review URL: http://codereview.chromium.org/267072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42445 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
0 files changed, 0 insertions, 0 deletions