- From: <bugzilla@jessica.w3.org>
- Date: Fri, 03 Jun 2011 02:57:12 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12870
Summary: Minor issues with WindowTimers domintro section and
timeout argument handling
Product: HTML WG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: cam@mcc.id.au
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
The green box refers to two different setTimeout calls, one of which has a
"code" argument the other has "handler". The IDL only has a "handler" version,
though.
Also, the description of how to "get the timeout" doesn't seem to match
implementations.
http://people.mozilla.org/~cmccormack/tests/timer-timeout.html shows
"ToNumber(timeout)" for Firefox, Safari, Chrome, Opera and IE. So we should be
able to just use floats for the timeouts.
So maybe we can write it as:
interface WindowTimers {
long setTimeout(in Function handler, in optional float timeout, in any...
args);
long setTimeout([AllowAny] in DOMString code, in optional float timeout, in
any... args);
void clearTimeout(in long handle);
long setInterval(in Function handler, in optional float timeout, in any...
args);
long setInterval([AllowAny] in DOMString code, in optional float timeout, in
any... args);
void clearInterval(in long handle);
};
and then simplify the "get the timeout" steps.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 3 June 2011 02:57:14 UTC