Changes between Version 146 and Version 147 of WebKitIDL

Timestamp:

Feb 25, 2016, 8:39:17 PM (9 years ago)

Author:

Chris Dumez

Comment:

Drop [TreatUndefinedAs=X]

WebKitIDL

@@ -8 +8 @@
 [#NamingRules Basic naming rules of IDL attributes][[br]]
 [#IDLAttributes IDL attributes]
- - [#TreatNullAs TreatNullAs(a,p), TreatUndefinedAs(a,p)][[br]]
+ - [#TreatNullAs TreatNullAs(a,p)][[br]]
  - [#Default Default(p)][[br]]
  - [#Clamp Clamp(a,p)][[br]]
@@ -225 +225 @@
 In the following explanations, (i), (m), (a) or (p) means that a given IDL attribute can be specified on interfaces, methods, attributes and parameters, respectively. For example, (a,p) means that the IDL attribute can be specified on attributes and parameters.
 
-== `[TreatNullAs]`(a,p), `[TreatUndefinedAs]`(a,p) == #TreatNullAs
+== `[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)
- * [http://dev.w3.org/2006/webapi/WebIDL/#TreatUndefinedAs The spec of TreatUndefinedAs] (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]` or `[TreatUndefinedAs=NullString]`.
+Usage: The possible usage is `[TreatNullAs=NullString]`.
 They can be specified on DOMString attributes or DOMString parameters only:
 {{{
     [TreatNullAs=NullString] attribute DOMString str;
-    void func([TreatNullAs=NullString, TreatUndefinedAs=NullString] DOMString str);
+    void func([TreatNullAs=NullString] DOMString str);
 }}}
 
@@ -245 +244 @@
 `[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.
-
-`[TreatUndefinedAs=NullString]` indicates that if a JavaScript undefined 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 `[TreatUndefinedAs=NullString]`, a JavaScript undefined is converted to a WebKit string "undefined".
-
-`[TreatUndefinedAs=NullString]` in WebKit corresponds to `[TreatUndefinedAs=EmptyString]` in the Web IDL spec.
-Unless the spec specifies `[TreatUndefinedAs=EmptyString]`, you should not specify `[TreatUndefinedAs=NullString]` in WebKit.
-
-Note: For now the sole usage of `[TreatUndefinedAs=NullString]` is not allowed.
-`[TreatUndefinedAs=NullString]` must be used with `[TreatNullAs=NullString]`, i.e. `[TreatNullAs=NullString, TreatUndefinedAs=NullString]`.
 
 == `[Default]`(p) == #Default