Timers in window interface

Maciej's initial draft [1] introduces a new TimerListener interface that is passed to the setTimeout and setInterval methods. This seems like a break to existing behaviour which is to pass a function or a string to be eval'ed. There has been some discussion on the lists about this design but no clear consensus. Clearly it's a goal to rationalise the window interface so that it fully supports DOM events but we also need to document existing behaviour.

My proposal is to keep setInterval/setTimer in their two argument function forms, i.e. they expect a function as first argument and a delay in milliseconds for the second. The parameter list form has been shown to be non-interoperable [2]. We don't endorse support for the string eval form.

We then define new events for the interval and timer - although I'm not sure about the mechanics at this stage. Should it be setIntervalListener?


Ian

[1] http://dev.w3.org/cvsweb/2006/webapi/Window/source/Window.xml
[2] http://lists.w3.org/Archives/Public/public-webapi/2006Feb/0050.html
 
To find out more about Library 2.0 and the Challenge of Disruptive Innovation, we invite you to read the latest white paper, listen to Talis' new Library 2.0 Gang podcasts and engage with us. 
Visit: www.talis.com/resources and www.talis.com/podcasts
Any views or personal opinions expressed within this email may not be those of Talis Information Ltd. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.