- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Jun 2012 01:34:48 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17612 Summary: I don't think [TreatNonCallableAsNull] is necessary on this callback, since if a non-Function is passed it will be converted to a string according to the other overload. That DOMString overload also doesn't need [AllowAny] as that is now the default beha Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#tim ers OS/Version: other Status: NEW Severity: normal Priority: P3 Component: other Hixie drafts (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#timers Complete: http://www.whatwg.org/c#timers Comment: I don't think [TreatNonCallableAsNull] is necessary on this callback, since if a non-Function is passed it will be converted to a string according to the other overload. That DOMString overload also doesn't need [AllowAny] as that is now the default behaviour for overload resolution. If you drop the [TreatNonCallableAsNull] then I think you can drop ArbitraryCallback and just reference http://dev.w3.org/2006/webapi/WebIDL/#common-Function. Posted from: 2001:44b8:4198:5700:cc00:74e7:2f56:df0d User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/16.0 Firefox/16.0a1 -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 27 June 2012 01:34:55 UTC