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

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

From: <bugzilla@jessica.w3.org>
Date: Sat, 29 Sep 2012 15:32:25 +0000
Message-Id: <E1THz1l-0007YW-JH@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19143

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> 2012-09-29 15:32:25 UTC ---
Given that all browsers agree here, I would worry about web compat issues with
changes.

In particular, I'm >70% confident that using unsigned long would break sites
that currently pass "-1" to setTimeout and expect that to mean "as soon as
possible", because it would suddenly mean "never".

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 29 September 2012 15:32:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:33 UTC