This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html Multipage: http://www.whatwg.org/C#timers Complete: http://www.whatwg.org/c#timers Comment: Nothing seems to define what the "any... args" parameters do. Posted from: 72.229.29.65 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.7 Safari/535.19
This is defined in <http://www.whatwg.org/C#get-the-timed-task>.
That's confusing. The invoking algorithms don't explicitly pass the arguments anywhere. Could the actual method descriptions mention what happens to the arguments somehow?
This bug was cloned to create bug 18160 as part of operation convergence.
The documentation above says "Any arguments are passed straight through to the handler", isn't that sufficient?
I always skip the author summaries and read the implementation requirements. As it stands, you can't figure out where they're actually used in the implementation requirements unless you click through every single link to identify the subalgorithms. I think it would be clearer if the the invoking methods made mention of the fact that they're passing the arguments. Callees referring to their callers' variables makes the logic harder to follow, in general -- although I grant that sometimes it's convenient and I do it too in writing spec algorithms.
(But anyway, I grant it's not a big deal and I'm not going to argue if you WONTFIX.)
I've been confused about this myself enough times that it's probably a bad idea for me to WONTFIX it. :-) I've made it explicit in the invokations of "get the timed task" that it uses those arguments.
Checked in as WHATWG revision r7271. Check-in comment: Clarify that 'get the timed task' uses the 1st and 3rd+ arguments of setTimeout/setInterval. http://html5.org/tools/web-apps-tracker?from=7270&to=7271