Changes between Version 143 and Version 144 of WebKitIDL


Ignore:
Timestamp:
Feb 24, 2016 4:53:19 PM (6 years ago)
Author:
Chris Dumez
Comment:

Drop TreatReturnedNullStringAs=False as this is NOT supported

Legend:

Unmodified
Added
Removed
Modified
  • WebKitIDL

    v143 v144  
    261261Summary: `[TreatReturnedNullStringAs]` controls the behavior when a WebKit null string is returned from the WebCore implementation.
    262262
    263 Usage: The possible usage is `[TreatReturnedNullStringAs=Null]`, `[TreatReturnedNullStringAs=Undefined]` or `[TreatReturnedNullStringAs=False]`.
     263Usage: The possible usage is `[TreatReturnedNullStringAs=Null]` or `[TreatReturnedNullStringAs=Undefined]`.
    264264They can be specified on DOMString attributes or methods that return a DOMString value:
    265265{{{
     
    270270 * `[TreatReturnedNullStringAs=Null]` indicates that if the returned DOMString is a WebKit null string, the returned value is treated as a JavaScript null.
    271271 * `[TreatReturnedNullStringAs=Undefined]` indicates that if the returned DOMString is a WebKit null string, the returned value is treated as a JavaScript undefined.
    272  * `[TreatReturnedNullStringAs=False]` indicates that if the returned DOMString is a WebKit null string, the returned value is treated as a JavaScript false.
    273272
    274273Without `[TreatReturnedNullStringAs=...]`, if the returned DOMString is a WebKit null string, then the returned value is treated as a JavaScript empty string ''.