GoogleCodeExporter
commented
8 years ago small typo on my behalf:
"then I got the JS error." should read "then I got the Java error."
Original comment by Ehrann.M...@gmail.com on 2 Sep 2012 at 4:26
Closed GoogleCodeExporter closed 8 years ago
GoogleCodeExporter
commented
8 years ago small typo on my behalf:
"then I got the JS error." should read "then I got the Java error."
Original comment by Ehrann.M...@gmail.com on 2 Sep 2012 at 4:26
GoogleCodeExporter
commented
8 years ago Thank you for the very accurate report.Original comment by peter.ry...@gmail.com on 2 Sep 2012 at 4:33
GoogleCodeExporter
commented
8 years ago Update - this only seems to happen to a file named main.js
I have no clue why...
other files seems to work well...Original comment by Ehrann.M...@gmail.com on 2 Sep 2012 at 4:38
GoogleCodeExporter
commented
8 years ago As absurd as it sounds, the cause of out of range by 2 positions problem is
that your file name is 2 characters shorter than we ever tried.
I suggest that you try with longer file names. The program will go on doing
something wrong inside, but hopefully you will move on.Original comment by peter.ry...@gmail.com on 2 Sep 2012 at 4:39
GoogleCodeExporter
commented
8 years ago As to your question:
yes, there should be possible to edit, set breakpoints, step over and push live
edits all from your local files. Thank you for the feedback such as this report.
What might be also important is what editor you are using for your sources. Is
it from any plugin you have installed in Eclipse? Or it is a standard common
plain text editor.Original comment by peter.ry...@gmail.com on 2 Sep 2012 at 4:45
GoogleCodeExporter
commented
8 years ago Ok, reading your comment about "main.js" – we definitely tried this name. My
guess about name length might be void then (I meant "x.js" from your example
originally).
Anyway, let me take a look at the code somewhat later.Original comment by peter.ry...@gmail.com on 2 Sep 2012 at 4:50
GoogleCodeExporter
commented
8 years ago I'm using the default JSDT javascript editor
issue reproduces also when I manual try to open main.js using the new "JS
Editor" that comes with the plugin...
regarding comment #5 - glad to hear, my question is - all of this is done via
the "JS Editor" that comes with the plugin? or via my "regular" editor (plain
text / JSDT)
it does work nicely with JSDT by the way, but then hovering a variable doesn't
do much
p.s. the quickest way to reproduce is just to open main.js with the JS editor
that comes with the plugin
not sure if it helps, but the file full path is "WebContent/js/main.js"Original comment by Ehrann.M...@gmail.com on 2 Sep 2012 at 5:26
GoogleCodeExporter
commented
8 years ago JSDT editor is going to improve adoption of chromedevtools breakpoints (disable
and properties actions) per https://bugs.eclipse.org/bugs/show_bug.cgi?id=389133Original comment by peter.ry...@gmail.com on 10 Sep 2012 at 10:46
GoogleCodeExporter
commented
8 years ago Fixed in 0.3.8Original comment by peter.ry...@gmail.com on 4 Oct 2012 at 8:35
Original issue reported on code.google.com by
Ehrann.M...@gmail.comon 2 Sep 2012 at 4:21