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 12870 - Minor issues with WindowTimers domintro section and timeout argument handling
Summary: Minor issues with WindowTimers domintro section and timeout argument handling
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 02:57 UTC by Cameron McCormack
Modified: 2011-08-10 00:16 UTC (History)
4 users (show)

See Also:


Attachments

Description Cameron McCormack 2011-06-03 02:57:11 UTC
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.
Comment 1 Michael[tm] Smith 2011-08-04 05:01:51 UTC
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-10 00:15:40 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Deferring to WebIDL is a goal, so I've changed it for that reason. Having the domintro and IDL blocks match isn't a goal.
Comment 3 contributor 2011-08-10 00:16:09 UTC
Checked in as WHATWG revision r6399.
Check-in comment: Defer to WebIDL more.
http://html5.org/tools/web-apps-tracker?from=6398&to=6399