Comment #5 on issue 22996 by [email protected]: Chrome Frame eats my
alt key
http://code.google.com/p/chromium/issues/detail?id=22996
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=27926
------------------------------------------------------------------------
r27926 | [email protected] | 2009-10-02 19:17:31 -0700 (Fri, 02 Oct 2009)
| 13 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_view_host.cc?r1=27926&r2=27925
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/tab_contents_view_gtk.cc?r1=27926&r2=27925
Pass unhandled keyup messages coming in from the renderer to the underlying
view. This is needed
for system keyboard messages which are generated when the Alt key is
pressed in addition to other
keys to function correctly in ChromeFrame.
The TabContentsView implementation for windows does the right thing by
specifically checking for keydown
events before processing them as accelerators. The TabContentsView
implementation for Linux also treated
keyup messages as accelerators, which is now fixed.
This fixes parts of http://code.google.com/p/chromium/issues/detail?id=22996
Bug=22996
Review URL: http://codereview.chromium.org/255028
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
