W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2012

[Bug 19143] setTimeout and setInterval should clamp at the maximum timeout value

From: <bugzilla@jessica.w3.org>
Date: Wed, 05 Dec 2012 21:01:35 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19143-2486-uvoLnp4B5T@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19143

Edward O'Connor <eoconnor@apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |eoconnor@apple.com
         Resolution|---                         |WONTFIX
           Assignee|erika.doyle@microsoft.com   |eoconnor@apple.com

--- Comment #4 from Edward O'Connor <eoconnor@apple.com> ---
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: Rejected
Change Description: No spec change.
Rationale: Given that all browsers currently interoperate, I don't think
we should risk the compat risk. The extant Web corpus has all sorts of
crazy values being passed to setTimeout.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 December 2012 21:01:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 5 December 2012 21:01:38 GMT