Remove IDBDatabaseException.{h,cpp}

By adding the IDB specific error names to DOMCoreException we can get
rid of IDBDatabaseException.{h,cpp}.

Now that no one is depending on the legacy error code enum inline
the legacy error codes into the table for DOMCoreException.

BUG=251411

Review URL: https://chromiumcodereview.appspot.com/17229006

git-svn-id: svn://svn.chromium.org/blink/trunk@153026 bbb929c8-8fbe-4397-9dbb-9b2b20218538

1 files changed, 2 insertions, 1 deletions

diff --git a/third_party/WebKit/Source/modules/indexeddb/IDBOpenDBRequest.cpp b/third_party/WebKit/Source/modules/indexeddb/IDBOpenDBRequest.cpp
index eac7261..bed1538 100644
--- a/third_party/WebKit/Source/modules/indexeddb/IDBOpenDBRequest.cpp
+++ b/third_party/WebKit/Source/modules/indexeddb/IDBOpenDBRequest.cpp
@@ -26,6 +26,7 @@
 #include "config.h"
 #include "modules/indexeddb/IDBOpenDBRequest.h"
 
+#include "core/dom/ExceptionCode.h"
 #include "core/dom/ScriptExecutionContext.h"
 #include "modules/indexeddb/IDBDatabase.h"
 #include "modules/indexeddb/IDBDatabaseCallbacksImpl.h"
@@ -150,7 +151,7 @@ bool IDBOpenDBRequest::dispatchEvent(PassRefPtr<Event> event)
     // an "error" event should be fired instead.
     if (event->type() == eventNames().successEvent && m_result->type() == IDBAny::IDBDatabaseType && m_result->idbDatabase()->isClosePending()) {
         m_result.clear();
-        onError(IDBDatabaseError::create(IDBDatabaseException::AbortError, "The connection was closed."));
+        onError(IDBDatabaseError::create(ABORT_ERR, "The connection was closed."));
         return false;
     }