diff options
| author | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-02-24 22:34:06 +0000 |
|---|---|---|
| committer | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-02-24 22:34:06 +0000 |
| commit | f6c2459d185424c66e4ef99eed7dc966039715e0 (patch) | |
| tree | 6e2ce58cadb57edeb57c8bfa2127191164fb3222 /chrome/chrome_tests.gypi | |
| parent | a6e82fccc2b73736c7a99e6293c6dfc04c6957ae (diff) | |
| download | chromium_src-f6c2459d185424c66e4ef99eed7dc966039715e0.zip chromium_src-f6c2459d185424c66e4ef99eed7dc966039715e0.tar.gz chromium_src-f6c2459d185424c66e4ef99eed7dc966039715e0.tar.bz2 | |
Don't re-run content scripts on fragment navigations.
This regression was inadvertently introduced by a fix to make executeScript
run after a fragment navigation (bug 29541). That patch was:
http://codereview.chromium.org/566041
The problem is that on frame navigations (didChangeLocationWithinPage), we end
up creating a new UserScriptIdleScheduler, so this patch keeps track of the
previous has_run state and propagates that to the new UserScriptIdleScheduler.
BUG=35924
TEST=Steps to verify are outlined in bug report
Review URL: http://codereview.chromium.org/646017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39939 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
| -rwxr-xr-x | chrome/chrome_tests.gypi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi index d377b95f..c1ba1c6 100755 --- a/chrome/chrome_tests.gypi +++ b/chrome/chrome_tests.gypi @@ -1161,6 +1161,7 @@ 'browser/extensions/extension_tabs_apitest.cc', 'browser/extensions/extension_toolbar_model_unittest.cc', 'browser/extensions/extension_toolstrip_apitest.cc', + 'browser/extensions/fragment_navigation_apitest.cc', 'browser/extensions/incognito_noscript_apitest.cc', 'browser/extensions/isolated_world_apitest.cc', 'browser/extensions/page_action_apitest.cc', |