Community
Participate
Working Groups
I think this was introduced as a side effect of Friday's changes for bug 328531. I've tried several pages with scripts that I've been using as test cases for a while, and it's now almost impossible to find a location that JSDT considers valid for setting a breakpoint. This makes Crossfire development difficult since most of it is used after a breakpoint has been hit.
(In reply to comment #0) > I think this was introduced as a side effect of Friday's changes for bug > 328531. I've tried several pages with scripts that I've been using as test > cases for a while, and it's now almost impossible to find a location that JSDT > considers valid for setting a breakpoint. This makes Crossfire development > difficult since most of it is used after a breakpoint has been hit. Can you attach some example scripts?
Created attachment 189978 [details] fix For some reason I added in code that checked if the resulting JavaScriptUnit had errors, and if so, do not allow a breakpoint to be set. Obviously we want to allow breakpoints to be set regardless of compilation problems in the script.
applied to HEAD, Grant please verify.