diff options
| author | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-08 05:18:22 +0000 |
|---|---|---|
| committer | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-08 05:18:22 +0000 |
| commit | e64fa3eab63110c9ac3864e6cf7ff3a94bed51d6 (patch) | |
| tree | e0aca02e90571d54c344d2a1b7b9d662793142e0 /webkit/glue | |
| parent | bd65a3dadac5b3b1127d37bcc78e9e3f009b664c (diff) | |
| download | chromium_src-e64fa3eab63110c9ac3864e6cf7ff3a94bed51d6.zip chromium_src-e64fa3eab63110c9ac3864e6cf7ff3a94bed51d6.tar.gz chromium_src-e64fa3eab63110c9ac3864e6cf7ff3a94bed51d6.tar.bz2 | |
Remove unneeded v8 lockers from idb_bindings.cc.
Since this code is pulled into webkit_unit_tests, it is making us
need lockers there too, which stinks.
I don't see any reason for these to exist. My speculation is that
this code used to run in the browser process and was needed at
that time.
BUG=
TEST=
Review URL: http://codereview.chromium.org/6812038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80895 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/glue')
| -rw-r--r-- | webkit/glue/idb_bindings.cc | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/webkit/glue/idb_bindings.cc b/webkit/glue/idb_bindings.cc index ae5b508..3149c52 100644 --- a/webkit/glue/idb_bindings.cc +++ b/webkit/glue/idb_bindings.cc @@ -12,7 +12,6 @@ #include "third_party/WebKit/Source/WebKit/chromium/public/WebIDBKeyPath.h" #include "third_party/WebKit/Source/WebKit/chromium/public/WebSerializedScriptValue.h" #include "third_party/WebKit/Source/WebKit/chromium/public/WebString.h" -#include "v8/include/v8.h" namespace webkit_glue { @@ -24,7 +23,6 @@ bool IDBKeysFromValuesAndKeyPath( const std::vector<WebSerializedScriptValue>& serialized_script_values, const string16& idb_key_path, std::vector<WebIDBKey>* values) { - v8::Locker lock; WebIDBKeyPath web_idb_key_path = WebIDBKeyPath::create(idb_key_path); bool error = web_idb_key_path.parseError() != 0; // TODO(bulach): what to do when we have a parse error? For now, setting @@ -46,7 +44,6 @@ WebSerializedScriptValue InjectIDBKey( const WebIDBKey& key, const WebSerializedScriptValue& value, const string16& idb_key_path) { - v8::Locker lock; return WebIDBKey::injectIDBKeyIntoSerializedValue( key, value, WebIDBKeyPath::create(idb_key_path)); } |