diff options
| author | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-24 18:10:36 +0000 |
|---|---|---|
| committer | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-24 18:10:36 +0000 |
| commit | 6e2d3d229024a3a0038c8a5c169bfd948a5c4939 (patch) | |
| tree | b9f37d0c4fc5758e2c0d4b4c407c3059ca59dd68 /content/content_tests.gypi | |
| parent | aee7b0822009cda31b7aea2922263a0b5adc6c9a (diff) | |
| download | chromium_src-6e2d3d229024a3a0038c8a5c169bfd948a5c4939.zip chromium_src-6e2d3d229024a3a0038c8a5c169bfd948a5c4939.tar.gz chromium_src-6e2d3d229024a3a0038c8a5c169bfd948a5c4939.tar.bz2 | |
Remove usage of WebKitContext from chrome. This also cleans up the chrome code so that it only calls profile-wide operations (i.e. saving session/purging memory/clearing local state on exit) on the BrowserContext. The content layer takes care of calling the necessary objects on the right thread.
WebKitContext now does almost nothing and I'll remove it completely in the next change.
BUG=98716
Review URL: https://chromiumcodereview.appspot.com/9462007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123509 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/content_tests.gypi')
| -rw-r--r-- | content/content_tests.gypi | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/content/content_tests.gypi b/content/content_tests.gypi index 7064833..fa10f86 100644 --- a/content/content_tests.gypi +++ b/content/content_tests.gypi @@ -221,7 +221,6 @@ 'browser/host_zoom_map_impl_unittest.cc', 'browser/in_process_webkit/dom_storage_unittest.cc', 'browser/in_process_webkit/indexed_db_quota_client_unittest.cc', - 'browser/in_process_webkit/webkit_context_unittest.cc', 'browser/in_process_webkit/webkit_thread_unittest.cc', 'browser/mac/closure_blocks_leopard_compat_unittest.cc', 'browser/mach_broker_mac_unittest.cc', |