From e1192af8726bcd25da58aba64b20d89e919230b9 Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Sat, 7 Jun 2014 14:22:49 -0400 Subject: Core: Work around loss of precision from parseFloat Fixes #15100 (cherry picked from commit b6e99eb43c35a3cd048c5c56d31c7e871f299a77) --- test/unit/core.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'test/unit') diff --git a/test/unit/core.js b/test/unit/core.js index d8631b02f..dac59d3d6 100644 --- a/test/unit/core.js +++ b/test/unit/core.js @@ -457,7 +457,7 @@ test("isFunction", function() { }); test( "isNumeric", function() { - expect( 37 ); + expect( 38 ); var t = jQuery.isNumeric, Traditionalists = /** @constructor */ function(n) { @@ -485,6 +485,7 @@ test( "isNumeric", function() { ok( t("4.536"), "Positive floating point string"); ok( t(-2.6), "Negative floating point number"); ok( t(3.1415), "Positive floating point number"); + ok( t(1.5999999999999999), "Very precise floating point number" ); ok( t(8e5), "Exponential notation"); ok( t("123e-2"), "Exponential notation string"); ok( t(answer), "Custom .toString returning number"); -- cgit v1.2.3