Remove FileError interface

third_party/WebKit/Source/core/fileapi/FileError.cpp

Index: third_party/WebKit/Source/core/fileapi/FileError.cpp
diff --git a/third_party/WebKit/Source/core/fileapi/FileError.cpp b/third_party/WebKit/Source/core/fileapi/FileError.cpp
index 4e17dd5ea0b9732594f2a3d7108fc8e575e53aa2..23eac4e71ed26fcbdaaf761cba3006ff13474111 100644
--- a/third_party/WebKit/Source/core/fileapi/FileError.cpp
+++ b/third_party/WebKit/Source/core/fileapi/FileError.cpp
@@ -31,6 +31,7 @@
 #include "core/fileapi/FileError.h"
 
 #include "bindings/core/v8/ExceptionState.h"
+#include "core/dom/DOMException.h"
 #include "core/dom/ExceptionCode.h"
 
 namespace blink {
@@ -136,9 +137,20 @@ void FileError::throwDOMException(ExceptionState& exceptionState, ErrorCode code
     exceptionState.throwDOMException(errorCodeToExceptionCode(code), errorCodeToMessage(code));
 }
 
+DOMException* FileError::createDOMException(ErrorCode code)
+{
+    DCHECK_NE(code, FileError::OK);
+
+    // TODO(jsbell): Special case SecurityError?

[jsbell, 2016/06/03 21:41:58]

I believe this is safe as it's only used in places that would have minted
FileError/DOMError instances before with just the same information, and the
message is completely generic anyway.

I could remove the special case entirely.

+    if (code == FileError::SECURITY_ERR) {
+        return DOMException::create(SecurityError, FileError::securityErrorMessage);
+    }
+
+    return DOMException::create(errorCodeToExceptionCode(code), errorCodeToMessage(code));
+}
+
 FileError::FileError(ErrorCode code)
-    : DOMError(DOMException::getErrorName(errorCodeToExceptionCode(code)), errorCodeToMessage(code))
-    , m_code(code)
+    : m_code(code)
 {
 }