Google Chrome version: Any
SDK full version: 0.1.0.200907072135
OS + version: Any
What steps will reproduce the problem?
1. Set a breakpoint in a script file
2. Reload the tab being debugged
What is the expected result?
The breakpoint is retained in the script file
What happens instead?
The breakpoint disappears and does not get hit during debugging.
Please provide additional information below. If possible, attach a
(reduced) test-case.
1) The breakpoints are set by script IDs rather than names (which is
nevertheless useful for V8 duplicate scripts) and
2) They are associated with resources that get removed and re-added when
the tab is reloaded
Original issue reported on code.google.com by apav...@chromium.org on 13 Jul 2009 at 4:08
Original issue reported on code.google.com by
apav...@chromium.org
on 13 Jul 2009 at 4:08