IDL: Fix handling of nullable NodeFilter / XPathNSResolver arguments

Source/bindings/scripts/v8_methods.py

Index: Source/bindings/scripts/v8_methods.py
diff --git a/Source/bindings/scripts/v8_methods.py b/Source/bindings/scripts/v8_methods.py
index e6bef2c0abf173263d7a3b64bd4d1c5b8638f09c..df33ebf1563e98cb1b904c9148f955182ba16a70 100644
--- a/Source/bindings/scripts/v8_methods.py
+++ b/Source/bindings/scripts/v8_methods.py
@@ -223,7 +223,8 @@ def cpp_value(interface, method, number_of_arguments):
                 return '%s.get()' % argument.name
             return argument.name
         if (idl_type.is_callback_interface or
-            idl_type.name in ['NodeFilter', 'XPathNSResolver']):
+            idl_type.name in ['NodeFilter', 'NodeFilterOrNull',

[Jens Widell, 2014/06/25 14:01:02]

For both NodeFilter and XPathNSResolver, the local variable will be of type
RefPtrWillBeRawPtr<X> and the argument will be of type
PassRefPtrWillBeRawPtr<X>. If I read RefPtr<>/PassRefPtr<> correctly, the
difference would be that the local holds on to a reference until it goes out of
scope without ".release()", and that's it. Should we just drop the special
casing?

With Oilpan and actual raw pointers, we will want to get rid of ".release()"
anyway, and then the effect will be that the local keeps the object alive until
it goes out of scope (at least.)

Note: is_callback_interface still needs the special casing, since it's sometimes
OwnPtr<>, where we certainly need to release.

+                              'XPathNSResolver', 'XPathNSResolverOrNull']):
             # FIXME: remove this special case
             return '%s.release()' % argument.name
         return argument.name