Changes between Version 79 and Version 80 of WebKitIDL

Timestamp:

Oct 12, 2012, 3:31:56 PM (12 years ago)

Author:

jsbell@chromium.org

Comment:

Add StrictTypeChecking on DOMString parameter details

WebKitIDL

@@ -15 +15 @@
  - [#Custom Custom(m,a), JSCustom(m,a), V8Custom(m,a), CustomGetter(a), JSCustomGetter(a), V8CustomGetter(a), CustomSetter(a), JSCustomSetter(a), V8CustomSetter(a)][[br]]
  - [#CallWith CallWith(i,m,a)][[br]]
- - [#StrictTypeChecking StrictTypeChecking(m,a)][[br]]
+ - [#StrictTypeChecking StrictTypeChecking(m,a,p)][[br]]
  - [#ReturnNewObject ReturnNewObject(m,a)][[br]]
  - [#ImplementedAs ImplementedAs(m,a)][[br]]
@@ -536 +536 @@
 For example, in case of func4(...), HTMLFoo::func3(ScriptArguments* arguments, ScriptCallStack* callstack, int a, int b) is called in WebCore.
 
-== [StrictTypeChecking](m,a) FIXME == #StrictTypeChecking
+== [StrictTypeChecking](m,a,p) FIXME == #StrictTypeChecking
 
 Summary: ADD SUMMARY
@@ -547 +547 @@
 
 ADD EXPLANATIONS
+
+V8 and 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(in [StrictTypeChecking] DOMString color);
+        void setColor(in float grayLevel);
+    };
+}}}
 
 == [ReturnNewObject](m,a) == #ReturnNewObject