Make several DOMImplementation API arguments mandatory

Source/core/dom/DOMImplementation.idl

Index: Source/core/dom/DOMImplementation.idl
diff --git a/Source/core/dom/DOMImplementation.idl b/Source/core/dom/DOMImplementation.idl
index 0d627f502f92107592dfa2d34ac0c0801e7d6ea0..b45c529871fbe6baf284aad2ccd029f702ad787f 100644
--- a/Source/core/dom/DOMImplementation.idl
+++ b/Source/core/dom/DOMImplementation.idl
@@ -24,17 +24,16 @@
 
     // DOM Level 1
 
-     boolean hasFeature([Default=Undefined] optional DOMString feature,
-                                      [TreatNullAs=NullString,Default=Undefined] optional DOMString version);
+     boolean hasFeature(DOMString feature, [TreatNullAs=NullString] DOMString version);

[arv (Not doing code reviews), 2013/08/14 15:08:22]

These changes make little sense. A nullable param in tail position is ripe for
being optional.

I'll file dom spec bugs

 
     // DOM Level 2
 
-     [RaisesException] DocumentType createDocumentType([TreatNullAs=NullString, TreatUndefinedAs=NullString,Default=Undefined] optional DOMString qualifiedName,
-                                                   [TreatNullAs=NullString, TreatUndefinedAs=NullString,Default=Undefined] optional DOMString publicId,
-                                                   [TreatNullAs=NullString, TreatUndefinedAs=NullString,Default=Undefined] optional DOMString systemId);
-     [RaisesException] Document createDocument([TreatNullAs=NullString,Default=Undefined] optional DOMString namespaceURI,
-                                           [TreatNullAs=NullString,Default=Undefined] optional DOMString qualifiedName,
-                                           [TreatNullAs=NullString,Default=Undefined] optional DocumentType doctype);
+     [RaisesException] DocumentType createDocumentType([TreatNullAs=NullString] DOMString qualifiedName,
+                                                       [TreatNullAs=NullString] DOMString publicId,
+                                                       [TreatNullAs=NullString] DOMString systemId);
+     [RaisesException] Document createDocument([TreatNullAs=NullString] DOMString namespaceURI,

[arv (Not doing code reviews), 2013/08/14 15:08:22]

I'm concerned about this one. I've seen people call this with less than 3
arguments (in webkit specific code but still).

[do-not-use, 2013/08/14 15:43:02]

I agree that the last argument could be optional since it is already nullable.

However, I believe the first argument only makes sense if the second one is
given. Also note that currently, if you omit the second argument
(qualifiedName), it will create a documentElement for the document with the
"undefined" string as tagName. This is unlikely to be what the caller wants IMO.

If we don't want to comply with the spec, I think we should add least add
[TreatUndefinedAs=NullString] for the second argument to avoid this weird
behavior.

+                                               [TreatNullAs=NullString] DOMString qualifiedName,
+                                               DocumentType doctype);
 
     // DOMImplementationCSS interface from DOM Level 2 CSS