Bug 171193

Summary: test262: test262/test/built-ins/Number/parseFloat.js
Product: WebKit Reporter: Joseph Pecoraro <joepeck>
Component: JavaScriptCoreAssignee: Joseph Pecoraro <joepeck>
Status: RESOLVED FIXED    
Severity: Normal CC: buildbot, commit-queue, joepeck, keith_miller, mark.lam, msaboff, saam, ysuzuki
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
[PATCH] Proposed Fix none

Joseph Pecoraro
Reported 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.
Attachments
[PATCH] Proposed Fix (8.21 KB, patch)
2017-04-23 02:04 PDT, Joseph Pecoraro
no flags
Joseph Pecoraro
Comment 1 2017-04-23 02:04:11 PDT
Created attachment 307926 [details] [PATCH] Proposed Fix
Yusuke Suzuki
Comment 2 2017-04-23 08:09:34 PDT
Comment on attachment 307926 [details] [PATCH] Proposed Fix r=me
WebKit Commit Bot
Comment 3 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>
WebKit Commit Bot
Comment 4 2017-04-23 08:37:58 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.