New issue
Advanced search Search tips

Issue 825394 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
susan.boorgula@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

wrong calculation

Reported by sinisa...@gmail.com, Mar 23 2018 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0

Steps to reproduce the problem:
1. run 0.55*100; in console
2. 
3. 

What is the expected behavior?
to get 55 as output

What went wrong?
output is : 55.00000000000001

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 29.0 r0

same result is in latest FireFox

Comment 1 by woxxom@gmail.com, Mar 24 2018 

The observed behavior is correct as per the JavaScript specification that defines numbers in IEEE 754 format:
http://www.ecma-international.org/ecma-262/8.0/index.html#sec-terms-and-definitions-number-value

You can find many explanations for the observed behavior, for example:
https://stackoverflow.com/questions/588004/is-floating-point-math-broken

Comment 2 by ajha@chromium.org, Mar 26 2018

Labels: Needs-Triage-M65

Comment 3 by susan.boorgula@chromium.org, Mar 26 2018

Cc: susan.boorgula@chromium.org
Labels: Triaged-ET M-67 Target-67 FoundIn-67 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
sinisanet@ Thanks for the issue.

Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac OS 10.12.6 on the latest Canary 67.0.3379.0 and Stable 65.0.3325.181.

On executing 0.55*100; in console, the output is 55.00000000000001.
Attached is the screen shot for reference.

This is a Non-Regression issue as this behavior is observed from M60 Chrome builds. 
Hence marking this as Untriaged for further updates from Dev.

Thanks..
825394.PNG
39.4 KB View Download

Comment 4 by dtapu...@chromium.org, Apr 9 2018

Status: WontFix (was: Untriaged)
Working as intended.
►

Sign in to add a comment