Closed Bug 164921 Opened 23 years ago Closed 23 years ago

Number.toString() has wrong value if the value of Number is greater than or equals 100000000000

Categories

(Core :: JavaScript Engine, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 140852

People

(Reporter: topperlu, Assigned: rogerl)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 value1 = 99999999999; value1.toString(); // we got 99999999999, OK value2 = 100000000000; value2.toString(); // we got 0:0000000000, Wrong value3 = 426067200000; value3.toString(); // we got 4260671:0000, Wrong Reproducible: Always Steps to Reproduce: 1.value = 426067200000; 2.value2.toString(); Actual Results: we got 4260671:0000, Wrong Expected Results: 426067200000;
Topper: good catch! We've only recently begun to understand this: bug 140852, "String(819187200000) == '8191871:0000' in xpcshell, browser" I'll go ahead and mark this as a duplicate. You will be cc'ed on bug 140852 so you can follow progress on this. *** This bug has been marked as a duplicate of 140852 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Marking Verified Duplicate -
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.