diff options
| author | dmazzoni@chromium.org <dmazzoni@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-23 15:48:26 +0000 |
|---|---|---|
| committer | dmazzoni@chromium.org <dmazzoni@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-23 15:48:26 +0000 |
| commit | 08100efefac6f4cf861f9b294a6cdebb7171c380 (patch) | |
| tree | f882304043ee02983ddcc606a2f916f87e72546c /tools/valgrind/common.py | |
| parent | 517d2fe72fd3e3ea3022279aab7e391be75804cf (diff) | |
| download | chromium_src-08100efefac6f4cf861f9b294a6cdebb7171c380.zip chromium_src-08100efefac6f4cf861f9b294a6cdebb7171c380.tar.gz chromium_src-08100efefac6f4cf861f9b294a6cdebb7171c380.tar.bz2 | |
Fix regression that stopped properly restoring focus to tab contents.
The bug in r51262 was that native_tab_contents_container_win overrides
RequestFocus, so it can't be *reliably* focused just using SetFocus.
This is a simple, straightforward fix that should be merged for M6.
Afterwards, I think a better solution for the dev channel would be to get rid
of the hacky RequestFocus overrides and add a View::HasNativeFocus method
so that FocusManager can tell when it thinks a view already has focus, but the
native focus might need to be set again. Thoughts?
BUG=48917
BUG=49061
TEST=none
Review URL: http://codereview.chromium.org/3013023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53471 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/valgrind/common.py')
0 files changed, 0 insertions, 0 deletions