70998 2011-10-27 01:26:04 -0700 Date constructor handles infinite values incorrectly. 2012-01-06 02:29:10 -0800 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED EasyFix P2 Normal --- 75692 0 mstarzinger webkit-unassigned ap barraclough oliver sam oldest_to_newest 491405 0 mstarzinger 2011-10-27 01:26:04 -0700 For cases in which the time value of a Date object is not a finite number, Date.prototype.toISOString() should throw a RangeError exception. This can either be reproduced by several Test262 test cases (i.e. 15.9.5.43-0-*) or with the following JavaScript snippet. function test() { var date = new Date(Infinity, 1, 70, 0, 0, 0); try { date.toISOString(); return false; } catch (e) { return e instanceof RangeError; } } 491689 1 ap 2011-10-27 10:27:11 -0700 Sounds much like bug 70394, but still happens in ToT. 491743 2 sam 2011-10-27 11:15:57 -0700 (In reply to comment #1) > Sounds much like bug 70394, but still happens in ToT. It is a different code path due to the Data constructor having different defined behavior when passing one argument, and two or more. 493184 3 barraclough 2011-10-31 00:12:42 -0700 To clarify Sam's comment, the issue re RangeErrors was fixed last week, in bug #70394 - the bug here is different. The problem is not in toISOString, but rather in the call to new Date. The test case assumes that the newly constructed Date has a NaN internal value; the bug is that it does not. You can demonstrate that toISOString behaved correctly by changing the arguments to new Date to ("") (which does correctly produce a Date with a NaN internal value). Retitling the bug accordingly. 530917 4 barraclough 2012-01-05 21:29:45 -0800 Fixed in r104267