bindings: Adds DOMArrayBuffer, etc. as thin wrappers for ArrayBuffer, etc.

Source/bindings/tests/results/core/V8SVGTestInterface.cpp

Index: Source/bindings/tests/results/core/V8SVGTestInterface.cpp
diff --git a/Source/bindings/tests/results/core/V8SVGTestInterface.cpp b/Source/bindings/tests/results/core/V8SVGTestInterface.cpp
index 62a65ec8ef3ecbaec426d1903abdf7617cc0f173..2a2d05250e5a20c9c716b07c5f24328fdc1c2dc8 100644
--- a/Source/bindings/tests/results/core/V8SVGTestInterface.cpp
+++ b/Source/bindings/tests/results/core/V8SVGTestInterface.cpp
@@ -104,7 +104,7 @@ v8::Handle<v8::Object> V8SVGTestInterface::findInstanceInPrototypeChain(v8::Hand
 
 SVGTestInterface* V8SVGTestInterface::toImplWithTypeCheck(v8::Isolate* isolate, v8::Handle<v8::Value> value)
 {
-    return hasInstance(value, isolate) ? blink::toScriptWrappableBase(v8::Handle<v8::Object>::Cast(value))->toImpl<SVGTestInterface>() : 0;
+    return hasInstance(value, isolate) ? toImpl(v8::Handle<v8::Object>::Cast(value)) : 0;

[haraken, 2014/10/16 05:41:41]

I still think this is a regression.

I agree that we cannot call toScriptWrappableBase()->toImpl for v8::ArrayBuffer
and its view, but only for v8::ArrayBuffer and its view. It shouldn't affect
other toImpl like SVGTestInterface.

[Yuki, 2014/10/16 14:21:51]

Okay, I added a {% if ... %} branch to the template.

 }