Bug 171193 - test262: test262/test/built-ins/Number/parseFloat.js
Summary: test262: test262/test/built-ins/Number/parseFloat.js
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Joseph Pecoraro
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-23 02:02 PDT by Joseph Pecoraro
Modified: 2017-04-23 08:37 PDT (History)
8 users (show)

See Also:


Attachments
[PATCH] Proposed Fix (8.21 KB, patch)
2017-04-23 02:04 PDT, Joseph Pecoraro
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Pecoraro 2017-04-23 02:02:30 PDT
test262/test/built-ins/Number/parseFloat.js

Test:

    assert( Number.parseFloat === parseFloat );

Notes:
- We already did this for parseInt, but not parseFloat!
- Chrome and Firefox pass.

Spec:

https://tc39.github.io/ecma262/#sec-number.parsefloat
20.1.2.12 Number.parseFloat ( string )

> The value of the Number.parseFloat data property is the same built-in
> function object that is the value of the parseFloat property of the
> global object defined in 18.2.4.
Comment 1 Joseph Pecoraro 2017-04-23 02:04:11 PDT
Created attachment 307926 [details]
[PATCH] Proposed Fix
Comment 2 Yusuke Suzuki 2017-04-23 08:09:34 PDT
Comment on attachment 307926 [details]
[PATCH] Proposed Fix

r=me
Comment 3 WebKit Commit Bot 2017-04-23 08:37:57 PDT
Comment on attachment 307926 [details]
[PATCH] Proposed Fix

Clearing flags on attachment: 307926

Committed r215673: <http://trac.webkit.org/changeset/215673>
Comment 4 WebKit Commit Bot 2017-04-23 08:37:58 PDT
All reviewed patches have been landed.  Closing bug.