Status: New
Owner: ----
New issue 2822 by [email protected]: Messages generated from custom error
events stringify as "[object Object]".
http://code.google.com/p/v8/issues/detail?id=2822
Copied from crbug.com/228909
---
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3)
AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31
Steps to reproduce the problem:
1. Go to this url: http://jsfiddle.net/salomvary/DVM6j/3/
2. Look at the "result" panel.
What is the expected behavior?
Should see "MyError: foo" there.
What went wrong?
I see "Uncaught [object Object]" there.
Looks like when an error is thrown which inherits from Error, when the
error is reported to window.onerror or console or developer tools,
something goes wrong when creating a string representation of the error
object.
Did this work before? Yes I detected the issue on the 4 Feb 2013, Chrome 25.
Chrome version: 26.0.1410.43 Channel: stable
OS Version: OS X 10.8.3
I'm not familiar with the v8/Chromium codebase but my guess is that the
problem is around here:
https://code.google.com/p/chromium/codesearch#chromium/src/v8/src/messages.js&q=%22Uncaught%22%20case:yes&sq=package:chromium&type=cs&l=205
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
