Support indexed setter generation

Source/bindings/tests/results/V8TestEventTarget.cpp

Index: Source/bindings/tests/results/V8TestEventTarget.cpp
diff --git a/Source/bindings/tests/results/V8TestEventTarget.cpp b/Source/bindings/tests/results/V8TestEventTarget.cpp
index 1b0fc3a7f21d4e4a8b552e1c454d32f101665808..f805295647b1b49e88759c13fde9c447178a872c 100644
--- a/Source/bindings/tests/results/V8TestEventTarget.cpp
+++ b/Source/bindings/tests/results/V8TestEventTarget.cpp
@@ -187,7 +187,7 @@ v8::Handle<v8::Value> V8TestEventTarget::namedPropertySetter(v8::Local<v8::Strin
     TestEventTarget* collection = toNative(info.Holder());
     V8TRYCATCH_FOR_V8STRINGRESOURCE(V8StringResource<>, propertyName, name);
     V8TRYCATCH_FOR_V8STRINGRESOURCE(V8StringResource<>, propertyValue, value);
-    bool result = collection->anonymousNamedSetter(propertyName, propertyValue);
+    bool result = collection->anonymousNamedSetter(propertyName, propertyValue, value->IsNull(), value->IsUndefined());

[kojih, 2013/05/28 06:51:28]

In HTMLSelectElement and HTMLOptionsCollection,
indexed setter remove the named element if JS value is null or undefined.
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit...

I think checking null/undefined in webcore layer is not special for
HTMLSelectElement and HTMLOptionsCollection,
so I added isValueNull and isValueUndefined parameter to all generated
indexed/named property setters.

[haraken, 2013/05/28 07:02:43]

This is dirty...

How do other browsers behave?

If we need to add these parameters, can we use optional parameters?

     if (!result)
         return v8Undefined();
     return value;