Issue metadata
Sign in to add a comment
|
[devtools] make TypeError descriptions more helpful
Reported by
kaycebas...@gmail.com,
Jun 14 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3129.0 Safari/537.36
Steps to reproduce the problem:
1. Evaluate `[a] = {a:1}` in the Console
What is the expected behavior?
Console outputs more useful information. For example, Firefox outputs `TypeError: ({a:1}) is not iterable`
What went wrong?
Console outputs `Uncaught TypeError: undefined is not a function at <anonymous>:1:1`
Did this work before? No
Chrome version: 61.0.3129.0 Channel: canary
OS Version: OS X 10.12.5
Flash Version:
source: https://twitter.com/bfred_it/status/874805874568470529
,
Jun 14 2017
Seems like a dupe of https://bugs.chromium.org/p/v8/issues/detail?id=5532
,
Jun 14 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lushnikov@chromium.org
, Jun 14 2017Status: Assigned (was: Unconfirmed)