diff options
| author | jochen@chromium.org <jochen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-23 02:49:05 +0000 |
|---|---|---|
| committer | jochen@chromium.org <jochen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-23 02:49:05 +0000 |
| commit | 8b68e2bd35dbe83be805a8665a264e977d66835c (patch) | |
| tree | 7a56673cb6651eb349051f257eed9144c2217bc2 /cc/test/layer_tree_pixel_test.cc | |
| parent | 51a4950fe59603ba5c5b0e29257fe6a286dd3d8c (diff) | |
| download | chromium_src-8b68e2bd35dbe83be805a8665a264e977d66835c.zip chromium_src-8b68e2bd35dbe83be805a8665a264e977d66835c.tar.gz chromium_src-8b68e2bd35dbe83be805a8665a264e977d66835c.tar.bz2 | |
[content shell] work around asynchronous history navigations killing layout tests
Between tests, we load about:blank into the RenderView to avoid stray navigation
signals from e.g. plugins. However, if a history navigation is pending, there might
be an IPC in flight and change which page we're displaying even after we've
navigated to about:blank.
Work around this issue by ensuring during resetting that we're indeed at about:blank.
BUG=111316
R=marja@chromium.org
TEST=we're not getting randomly killed for invalid navigations
Review URL: https://codereview.chromium.org/12921005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189974 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/test/layer_tree_pixel_test.cc')
0 files changed, 0 insertions, 0 deletions