Changes between Version 147 and Version 148 of WebKitIDL

Timestamp:

Feb 29, 2016, 11:31:36 AM (9 years ago)

Author:

Chris Dumez

Comment:

[TreatNullAs=EmptyString]

WebKitIDL

@@ -227 +227 @@
 == `[TreatNullAs]`(a,p) == #TreatNullAs
 
- * [http://dev.w3.org/2006/webapi/WebIDL/#TreatNullAs The spec of TreatNullAs] (Note: The WebKit behavior explained below is different from the spec)
-
-Summary: They control the behavior when a JavaScript null or undefined is passed to a DOMString attribute or parameter.
-
-Usage: The possible usage is `[TreatNullAs=NullString]`.
+ * [http://heycam.github.io/webidl/#TreatNullAs The spec of TreatNullAs]
+
+Summary: When a JavaScript null is passed to a DOMString attribute or parameter, its gets converted to the empty string "" internally instead of being stringified as the string "null".
+
+Usage: The possible usage is `[TreatNullAs=EmptyString]`.
 They can be specified on DOMString attributes or DOMString parameters only:
 {{{
-    [TreatNullAs=NullString] attribute DOMString str;
-    void func([TreatNullAs=NullString] DOMString str);
-}}}
-
-`[TreatNullAs=NullString]` indicates that if a JavaScript null is passed to the attribute or parameter,
-then it is converted to a WebKit null string, for which both String::IsEmpty() and String::IsNull() will return true.
-Without `[TreatNullAs=NullString]`, a JavaScript null is converted to a WebKit string "null".
-
-`[TreatNullAs=NullString]` in WebKit corresponds to `[TreatNullAs=EmptyString]` in the Web IDL spec.
-Unless the spec specifies `[TreatNullAs=EmptyString]`, you should not specify `[TreatNullAs=NullString]` in WebKit.
+    [TreatNullAs= EmptyString] attribute DOMString str;
+    void func([TreatNullAs= EmptyString] DOMString str);
+}}}
 
 == `[Default]`(p) == #Default