Issue metadata
Sign in to add a comment
|
Object.entries sometimes passes an incorrect value to callback function
Reported by
grygabri...@gmail.com,
Mar 13 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36 Steps to reproduce the problem: 1. Use Chrome 65 2. Use Object.entries on a variety of objects (unclear what the criteria are to trigger this bug) 3. Observe that sometimes the second item in the array passed to the callback function will be a string instead of the actual value from the object. What is the expected behavior? Object.entries should always pass a key and the correct corresponding value to the callback function. What went wrong? Updated to Chrome 65, and suddenly my app that makes liberal use of Object.entries is broken. Debugging led me to discover that some objects will produce this problem, others will not. It is not clear what triggers this bug. Forcing use of the MDN polyfill fixes the issue. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/entries#Polyfill Did this work before? Yes 64 Chrome version: 65.0.3325.146 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Mar 13 2018
Meanwhile you can use Chrome Canary, which is installed separately.
,
Mar 13 2018
Sorry for the dupe! Apparently I suck at searching.
,
Mar 13 2018
This bugtracker doesn't show fixed bugs by default unless you explicitly switch the search scope.
,
Mar 14 2018
,
Mar 14 2018
As per comment#1 and comment#3 this seems to be a duplicate of issue 804159 . Hence merging into and removing Needs-Bisect label. Please feel free to change if it is not same. Thanks! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by woxxom@gmail.com
, Mar 13 2018