Changes between Version 152 and Version 153 of WebKitIDL

Timestamp:

Aug 2, 2016, 12:12:39 PM (9 years ago)

Author:

Chris Dumez

Comment:

StrictTypeChecking no longer exists as of r204033

WebKitIDL

@@ -13 +13 @@
  - [#CustomBinding CustomBinding][[br]]
  - [#CallWith CallWith(m,a), SetterCallWith(a)][[br]]
- - [#StrictTypeChecking StrictTypeChecking(m,a,p)][[br]]
  - [#NewObject NewObject(m,a)][[br]]
  - [#ImplementedAs ImplementedAs(m,a)][[br]]
@@ -414 +413 @@
 For example, in case of `func4(...)`, `HTMLFoo::func3(ScriptArguments* arguments, ScriptCallStack* callstack, int a, int b)` is called in WebCore.
 
-== `[StrictTypeChecking]`(m,a,p) FIXME == #StrictTypeChecking
-
-Summary: ADD SUMMARY
-
-Usage: `[StrictTypeChecking]` can be specified on methods and attributes:
-{{{
-    [StringTypeChecking] attribute float x;
-    [StrictTypeChecking] DOMString func();
-}}}
-
-ADD EXPLANATIONS
-
-JSC: `[StrictTypeChecking]` can also be applied to a DOMString parameter in an overloaded method to make the
-overload resolution only match for ECMAScript types null, undefined, string or object - and not number or boolean.
-This is to permit overloads which are not "distinguishable" in WebIDL, for example:
-
-{{{
-    interface CanvasFoo {
-        void setColor([StrictTypeChecking] DOMString color);
-        void setColor(float grayLevel);
-    };
-}}}
-
 == `[NewObject]`(m,a) == #NewObject