Comment #3 on issue 22852 by [email protected]: parse errors aren't
logged to the console on refresh
http://code.google.com/p/chromium/issues/detail?id=22852
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=27067
------------------------------------------------------------------------
r27067 | [email protected] | 2009-09-24 08:16:18 -0700 (Thu, 24 Sep 2009) |
6 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/debugger/devtools_sanity_unittest.cc?r1=27067&r2=27066
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/devtools/script_syntax_error.html
M
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/glue/devtools/js/debugger_agent.js?r1=27067&r2=27066
M
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/glue/devtools/js/tests.js?r1=27067&r2=27066
DevTools: autoresume execution on parse errors.
BUG=22852
TEST=DevToolsSanityTest.TestAutoContinueOnSyntaxError
Review URL: http://codereview.chromium.org/218026
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
