You're right, I didn't realise you could do that. Restarting only the
javascript debugger tab takes around 4s to refresh the page, which is
acceptable. Hopefully others will find this work around useful too.
On Tuesday, September 22, 2015 at 3:26:24 PM UTC+1, Jens wrote:
>
> Yeah really seems to
Yeah really seems to be broken after reloading Chrome. As a workaround
instead of reloading Chrome manually, just restart the JavaScript Debug run
configuration in IntelliJ which also triggers a reload (and possibly a
recompilation if you changed code) in Chrome. A bit unusual workflow but it
w
I've just updated to latest, ideaIU-141.2734.1.dmg, on OSX Yosemite. I
un-installed and re-install the JetBrains Chrome extension. I invalidated
the cache and restarted IntelliJ. However the behaviour is the same. When I
start the debug session it'll launch Chrome and debug without a problem. If
It seems there is something temperamental about this. I upgraded to 14.1.4
and the problem is still there, other members in my team tried as well -
without luck.
Anyone else having problems with this on the latest stable version of
IntelliJ?
Mark
On Thursday, August 27, 2015 at 12:27:48 PM UT
I have had this problem too. Updating to the most recent version of
IntelliJ IDEA (14.1.4) solved the problem.
Op donderdag 27 augustus 2015 01:11:22 UTC+2 schreef Thanos:
>
> Is IntelliJ debug and break points working for anyone? It seems to be
> broken right now. The breakpoint works when runn
Is IntelliJ debug and break points working for anyone? It seems to be
broken right now. The breakpoint works when running for the first time in
the browser, if you do a refresh the break points no longer work. I've seen
these two JIRAs, and "bumped" one, hoping we can get some feedback.
https://