diff options
| author | estade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-08 19:01:11 +0000 |
|---|---|---|
| committer | estade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-08 19:01:11 +0000 |
| commit | 7a1f7a2f2bf0c09d2767a496a09509898d4aaa02 (patch) | |
| tree | 6a10586956ec2b8b9ad6cfffc742e5d069bb1138 /chrome/browser/browsing_instance.cc | |
| parent | 0f38ceaebbc66b29fb3297516f74f9c8379d902f (diff) | |
| download | chromium_src-7a1f7a2f2bf0c09d2767a496a09509898d4aaa02.zip chromium_src-7a1f7a2f2bf0c09d2767a496a09509898d4aaa02.tar.gz chromium_src-7a1f7a2f2bf0c09d2767a496a09509898d4aaa02.tar.bz2 | |
Linux: clean up some focus issues.
- Set focus to render view after finishing find.
- Make all custom buttons unfocusable. (matches windows chrome)
- Let the GtkWindow's default keyhandler run when the child widget fails to handle the key press event. Previously I optimized this out, but it turns out to be necessary because when a tab is pressed while focus is at the boundary of a child widget (e.g. the last button in an infobar) the focus has to traverse to the next child widget (e.g. the render view), and this is handled by the GtkWindow's key handler (and not the infobar's key handler).
BUG=8604,11560
Review URL: http://codereview.chromium.org/115113
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15666 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browsing_instance.cc')
0 files changed, 0 insertions, 0 deletions