Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(141)

Issue 155555: A quick fix for Issue 13711 (the second part)... (Closed)

Created:
11 years, 5 months ago by Hironori Bono
Modified:
9 years, 7 months ago
Reviewers:
Evan Martin, Evan Stade
CC:
chromium-reviews_googlegroups.com, brettw, Ben Goodger (Google)
Visibility:
Public.

Description

A quick fix for Issue 13711 (the second part) Because of a hard-disk problem, I lost the original change. So, I would like to send another change for this fix. This is the second part of the fix for Issue 13711. On non-ASCII keyboards (e.g. Russian and Hebrew), |event->keyval| represents a non-ASCII value that BrowserWindowGtk::HandleAccelerator() cannot handle. To fix this issue, this change uses |event->hardware_keycode| to retrieve its ASCII value before calling BrowserWindowGtk::HandleAccelerator(). BUG=13711 "Alt-D does not work when in editbox" TEST=Type alt+d keys on a Russian keyboard and verify the input focus is moved to an onmibox. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=20944

Patch Set 1 #

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+88 lines, -1 line) Patch
M chrome/browser/tab_contents/tab_contents_view_gtk.cc View 1 3 chunks +88 lines, -1 line 0 comments Download

Messages

Total messages: 2 (0 generated)
Hironori Bono
11 years, 5 months ago (2009-07-15 09:50:50 UTC) #1
Evan Martin
11 years, 5 months ago (2009-07-15 16:55:42 UTC) #2
LGTM if this is the same as before.

I'm still a little frightened of these changes.  Do you have any ideas of how we
can create tests to cover all of the input cases?

Powered by Google App Engine
This is Rietveld 408576698