This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16019 - Nothing seems to define what the "any... args" parameters do.
Summary: Nothing seems to define what the "any... args" parameters do.
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on:
Reported: 2012-02-17 17:55 UTC by contributor
Modified: 2012-08-24 22:22 UTC (History)
4 users (show)

See Also:


Description contributor 2012-02-17 17:55:42 UTC

Nothing seems to define what the "any... args" parameters do.

Posted from:
User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.7 Safari/535.19
Comment 1 Ms2ger 2012-05-14 16:49:48 UTC
This is defined in <>.
Comment 2 Aryeh Gregor 2012-05-15 05:55:45 UTC
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?
Comment 3 contributor 2012-07-18 17:29:29 UTC
This bug was cloned to create bug 18160 as part of operation convergence.
Comment 4 Ian 'Hixie' Hickson 2012-07-23 05:12:14 UTC
The documentation above says "Any arguments are passed straight through to the handler", isn't that sufficient?
Comment 5 Aryeh Gregor 2012-07-23 09:36:40 UTC
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.
Comment 6 Aryeh Gregor 2012-07-23 09:37:04 UTC
(But anyway, I grant it's not a big deal and I'm not going to argue if you WONTFIX.)
Comment 7 Ian 'Hixie' Hickson 2012-08-24 22:22:11 UTC
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.
Comment 8 contributor 2012-08-24 22:22:47 UTC
Checked in as WHATWG revision r7271.
Check-in comment: Clarify that 'get the timed task' uses the 1st and 3rd+ arguments of setTimeout/setInterval.