diff options
| author | jochen@chromium.org <jochen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-22 22:27:45 +0000 |
|---|---|---|
| committer | jochen@chromium.org <jochen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-22 22:27:45 +0000 |
| commit | 37d9dccef3f855d2bbe843a5d519c11ed33c41d5 (patch) | |
| tree | 5562604adc21f9fb1b3d144ed697828ca8385af6 /media/ffmpeg/ffmpeg_regression_tests.cc | |
| parent | 4b44ed4d2d231ca462794dbf07886a02943d6463 (diff) | |
| download | chromium_src-37d9dccef3f855d2bbe843a5d519c11ed33c41d5.zip chromium_src-37d9dccef3f855d2bbe843a5d519c11ed33c41d5.tar.gz chromium_src-37d9dccef3f855d2bbe843a5d519c11ed33c41d5.tar.bz2 | |
[content shell] always focus the frame that was navigated
Otherwise, when the focused frame is destroyed, we end up with no
frame focused at all.
This approach is a bit crude (doesn't do anything if the page
itself initiated the navigation, changes the focus also if we're
staying on the page), but it's good enough for layout tests
BUG=111316
R=marja@chromium.org
TEST=e.g. running fast/inline/25277-2.html after fast/frames/frame-dead-region.html doesn't fail
Review URL: https://codereview.chromium.org/12893008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189927 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/ffmpeg/ffmpeg_regression_tests.cc')
0 files changed, 0 insertions, 0 deletions