WebStorm Issue with Live Edit in Chrome since 129.541

I know that when the Chrome debugger is open Live Edit (live updating of css) doesn't work, however previously, once I shut the Chrome debugger live edit would start to work again.

A common workflow for me was using live edit for a while, then open Chrome debugger to check something, close it and go back to live editing.

However I noted that in the past few days and it seems to have coincided with build 129.541, once I have opened the Chrome debugger live edit can't reconnect to that tab, even when I close the debugger or even refresh the page, the only way to get live edit working again is to reopen the page in another browser tab.

Has anyone seen a similar issue?
Rob

7 comments

Hi Robert,

I've faced it as well. Logged as http://youtrack.jetbrains.com/issue/WEB-7922

Best regards,
Lena

0

Seems the issue is fixed in WebStorm 7 EAP build 130.753 (May 29th)

Rob

0

no but it seems like my crap is fizzling out also.  I have a post up whereas I was using local debug for a while, able to step into my debug points in WS for about 2 months, and then all of a sudden WS decides to stop working as in I can't debug anymore period (chrome OR FF).  Nothing really changed to cause that on my end either.  It's like WTF, WS just decides to suddendly act differently both in the UI itself and now the chrome plugin is being a pain in the ass showing that it's not connected anymore.

I've got a friend who uses WS in a java environment, has none of these issues.  What's up with WS and windows?  I amost feel as though us Windows users are second to other OS's in terms of testing/QA and overall bug fixes for our end of the spectrum vs. non Windows version of WS.

0

Well the issue I reported is fixed - however I agree your comments about debugging in general.

I have rarely if ever been able to debug with WS, main problem for me it would never stop on the breakpoints even though the debugger connected and could pick up console logging.

I just tried it in WS7 and if anything it worse - the web page opens but doesnt load and is blank and the chrome busy spinner just goes forever.....

If I then click stop debugging the page which diconnects then the page immediately loads.

Rob

0
I have rarely if ever been able to debug with WS, main problem for me it would never stop on the breakpoints even though the debugger connected and could pick up console logging.



Precisely what I've experienced lately.

I just tried it in WS7 and if anything it worse - the web page opens but doesnt load and is blank and the chrome busy spinner just goes forever.....


Funny I'm still using 6 and at the same time my debug points stopped being hit, I noticed that now when I debug via Chrome (local debug settings) it used to just add a new tab in my existing chrome instance, but now when I start debug in WS, all of a sudden a couple weeks ago it decides "Hey why not open an entire new instance of Chrome instead of staying consistent with what I was doing, adding a new tab for the developer for debugging and loading the page in Chrome".

I just don't get how these types of bugs can bypass QA, and I wonder if JetBrains is doing any QA or TDD/XP.  That may be the entire problem, not enough focus on TDD and/or QA who knows.  I obviously have no insight but totally frustrated as I'm seeing people with the same issues all over and I just am not a happy camper when it WAS working which is WHY I bougth it a month ago and now it's just broken for no reason.

great and I just purchased WS.  The whole benefit or at least major benefit was I was able to use WS's great debugging tools.  Not sure what the hell I'll do now, wasted $50 potentially.  I'm very frustrated as anyone reading this can tell.

I'm gonna reference my threads so we can continue the discussion here if anyone wishes to and has the same issues I'm having (running Windows 7 64-bit Pro):

Chrome Plug-in continually in "Not Connected" State

0

Well IMHO WS is by far the best Web IDE available today - I have been using it for the last two years or so and think its brilliant!!
Its a major productivity boost and well worth the $50.


- the only real issue is the debugger -

but that has never really bothered me very much because Chrome's built in debugger is very good  - though I would like to be able to use a debugger integrated into the IDE.

Definitely not a waste of money, I am sure you will grow to love it :)
Rob

0
Well IMHO WS is by far the best Web IDE available today


yea...WHEN it works I totally agree...which is why I'm so frustrated...I want to use WS, I was so phsyced when I did started using it 3 mo ago, let all my collegues know how great it is and now it's junk as it's not doing crap for me in terms of debug.  When you have a tool that is awesome WHEN it works or when it decides to work, and then go from that to not working and paying $50, who wouldn't be pissed off or extremly disappointed.  I want to use this thing!  Believe me!  I do love it but how can I grow to love it when one of the best parts of WS is its debugging capability when the damn thing just stops working!

What's the point of using it if you can't use its features due to the fact that the app keeps breaking via chore functionality.  It totally stomps out its usefulness.

I find it odd that my friend who is not using a Windows OS says he has never seen any of the issues we are describing in a Windows environment.  Something is not right with JetBrains here as far as R&D and QA.

0

Please sign in to leave a comment.