diff options
| author | michaeln@google.com <michaeln@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-04 02:26:56 +0000 |
|---|---|---|
| committer | michaeln@google.com <michaeln@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-04 02:26:56 +0000 |
| commit | 5b088adf98cdd69d48500af0974c701cc3aa60a8 (patch) | |
| tree | 8360b7785ff9a006a7092d5a334b4c33ccf667a5 /chrome/browser/page_info_model.cc | |
| parent | 806907a2790ade5b63daffad3e1ce2a0f43b32e2 (diff) | |
| download | chromium_src-5b088adf98cdd69d48500af0974c701cc3aa60a8.zip chromium_src-5b088adf98cdd69d48500af0974c701cc3aa60a8.tar.gz chromium_src-5b088adf98cdd69d48500af0974c701cc3aa60a8.tar.bz2 | |
Call webkit init once for all chrome unit tests and move the only unittest
that was initting webkit itself to the browsertest harness where each
test is expected to init webkit. Initting webkit is useful for two reasons:
1. It allows the use of some primitive webkit data types like WebString and WebSecurityOrigin.
2. Individual unittests should not be initting webkit on their own, initting
it here ensures attempts to do so within an individual test will fail.
BUG=52357
TEST=none
Review URL: http://codereview.chromium.org/6291007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@73743 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/page_info_model.cc')
0 files changed, 0 insertions, 0 deletions