Status: Untriaged Owner: [email protected] Labels: Type-Bug Pri-2 OS-All Area-DevTools
New issue 25172 by [email protected]: Debugger fails to report what the error is that caused it to stop http://code.google.com/p/chromium/issues/detail?id=25172 What steps will reproduce the problem? 1. Open JavaScript console in Chrome. 2. Open attached error1.html or error2.html. What is the expected output? What do you see instead? Expected: Debugger stops and reports error message in console. Actual: Debugger stops but does not report error message in console. For both test cases, Safari's debugger properly reports the errors. Attachments: error1.html 105 bytes error1.js 641 bytes error2.html 105 bytes error2.js 953 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
