Changes between Version 145 and Version 146 of WebKitIDL

Timestamp:

Feb 25, 2016, 3:14:56 PM (10 years ago)

Author:

Chris Dumez

Comment:

[TreatReturnedNullStringAs=X] was dropped

WebKitIDL

@@ -9 +9 @@
 [#IDLAttributes IDL attributes]
  - [#TreatNullAs TreatNullAs(a,p), TreatUndefinedAs(a,p)][[br]]
- - [#TreatReturnedNullStringAs TreatReturnedNullStringAs(m,a)][[br]]
  - [#Default Default(p)][[br]]
  - [#Clamp Clamp(a,p)][[br]]
@@ -257 +256 @@
 `[TreatUndefinedAs=NullString]` must be used with `[TreatNullAs=NullString]`, i.e. `[TreatNullAs=NullString, TreatUndefinedAs=NullString]`.
 
-== `[TreatReturnedNullStringAs]`(m,a) == #TreatReturnedNullStringAs
-
-Summary: `[TreatReturnedNullStringAs]` controls the behavior when a WebKit null string is returned from the WebCore implementation.
-
-Usage: The possible usage is `[TreatReturnedNullStringAs=Undefined]`.
-They can be specified on DOMString attributes or methods that return a DOMString value:
-{{{
-    [TreatReturnedNullStringAs= Undefined] attribute DOMString str;
-    [TreatReturnedNullStringAs=Undefined] DOMString func();
-}}}
-
- * `[TreatReturnedNullStringAs=Undefined]` indicates that if the returned DOMString is a WebKit null string, the returned value is treated as a JavaScript undefined.
-
-Without `[TreatReturnedNullStringAs=...]`, if the returned DOMString is a WebKit null string, then the returned value is treated as a JavaScript empty string ''.
-
 == `[Default]`(p) == #Default