25630 2014-05-09 08:15:00 +0000 "The following use of overloading however is inv..." 2017-07-28 14:41:06 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified All All RESOLVED DUPLICATE 23879 P2 minor --- 1 nbarth+w3bugzilla cam annevk mike public-script-coord tobie.langel public-webapps-bugzilla oldest_to_newest 105529 0 nbarth+w3bugzilla 2014-05-09 08:15:00 +0000 http://heycam.github.io/webidl/#idl-overloading This is outdated: [[ The following use of overloading however is invalid: IDL interface B { void f(DOMString x); void f(float x); }; since DOMString and float are not distinguishable. ]] ...since DOMStrings and floats (numerics) are now distinguishable. This can be corrected by replacing "DOMString" with "long": [[ The following use of overloading however is invalid: IDL interface B { void f(long x); void f(float x); }; since long and float are not distinguishable. ]] 105694 1 annevk 2014-05-12 09:02:10 +0000 I think it's still invalid to accept both string and number because it's unclear whether you should use ToString or ToNumber. 105698 2 nbarth+w3bugzilla 2014-05-12 09:19:22 +0000 AFAICT, String vs. Number is handled in the overload resolution algorithm (nutshell: if argument is a Number, resolve to numeric if possible; otherwise use ToString if possible, otherwise use ToNumber if possible) http://heycam.github.io/webidl/#dfn-overload-resolution-algorithm In detail: 10. Otherwise: if V is a Number value, and there is an entry in S that has one of the following types at position i of its type list, • a numeric type ... 11. Otherwise: if there is an entry in S that has one of the following types at position i of its type list, • DOMString ... 12. Otherwise: if there is an entry in S that has one of the following types at position i of its type list, • a numeric type ... 128799 3 tobie.langel 2017-07-28 14:41:06 +0000 *** This bug has been marked as a duplicate of bug 23879 ***