diff options
author | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-04-04 21:32:40 +0000 |
---|---|---|
committer | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-04-04 21:32:40 +0000 |
commit | 965524b257d99bbc4c10e82a1294ed1f91516e2c (patch) | |
tree | e23e34f5a12b995a10b94b726f36a59dc32393f8 /chrome/browser/tab_contents/navigation_entry.h | |
parent | 2b4355c4590724ae676f0ec5a8230e5c8c4cddf9 (diff) | |
download | chromium_src-965524b257d99bbc4c10e82a1294ed1f91516e2c.zip chromium_src-965524b257d99bbc4c10e82a1294ed1f91516e2c.tar.gz chromium_src-965524b257d99bbc4c10e82a1294ed1f91516e2c.tar.bz2 |
Remove some uses of custom tab contents types from some tests.
This required redoing the tests that used it to use the new RenderViewHost
test harness. This is mostly straightforward, but required more work for the
NavigationController tests.
I removed a few random places that were testing for the tab types. I also
made different versions of a few functions that don't take tab contents types
next to the existing ones that do, so my touched code won't have to be changed
again when I remove the tab contents types.
Review URL: http://codereview.chromium.org/62039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13132 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/tab_contents/navigation_entry.h')
-rw-r--r-- | chrome/browser/tab_contents/navigation_entry.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chrome/browser/tab_contents/navigation_entry.h b/chrome/browser/tab_contents/navigation_entry.h index 16801b3..9a39d14 100644 --- a/chrome/browser/tab_contents/navigation_entry.h +++ b/chrome/browser/tab_contents/navigation_entry.h @@ -174,6 +174,7 @@ class NavigationEntry { // --------------------------------------------------------------------------- + NavigationEntry(); explicit NavigationEntry(TabContentsType type); NavigationEntry(TabContentsType type, SiteInstance* instance, @@ -290,9 +291,8 @@ class NavigationEntry { // state properly when the user goes back and forward. // // WARNING: This state is saved to the file and used to restore previous - // states. If you write a custom TabContents and provide your own state make - // sure you have the ability to modify the format in the future while being - // able to deal with older versions. + // states. If the format is modified in the future, we should still be able to + // deal with older versions. void set_content_state(const std::string& state) { content_state_ = state; } |