New issue
Advanced search Search tips

Issue 129539 link

Starred by 1273 users

Issue metadata

Status: Fixed
Closed: Oct 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

issue chromedriver:483
issue 449847

  • Only users with EditIssue permission may comment.

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment

opening embedded Developer Tools will terminate the remote connection

Reported by, May 24 2012

Issue description

I cannot find issue for "opening embedded Developer Tools will terminate the remote connection / detach the extension and will replace active debugger with itself. We are working on allowing several clients to instrument the page simultaneously" ( Are there any plans about it?

Comment 1 by, May 24 2012

Labels: -Area-Undefined Area-UI Feature-DevTools
Any news regarding this issue?
Project Member

Comment 3 by, Aug 10 2012

Labels: -Pri-2 pri-1 Action-NeedsReview
Summary: opening embedded Developer Tools will terminate the remote connection
There were at least 10 stars on this issue, in the last 90 days, increasing priority for review.

Comment 4 by, Aug 10 2012

Labels: -Action-NeedsReview Mstone-23
Status: Assigned

Comment 6 by, Oct 10 2012

Labels: -Mstone-23 MovedFrom-23 Mstone-24
Moving all non essential bugs to the next Milestone
Labels: -MovedFrom-23 -Mstone-24 Mstone-27
Project Member

Comment 8 by, Nov 2 2012

The following revision refers to this bug:

r165656 | | 2012-11-02T11:20:51.359374Z

Changed paths:

DevTools: [remote debugging] emit Inspector.detached protocol message upon connectin termination. 

BUG= 129539 

As the above changeset indicates: there is now a reason field in the protocol to indicate why the connection was detached:
Project Member

Comment 10 by, Mar 10 2013

Labels: -Area-UI -Feature-DevTools -Mstone-27 Cr-UI Cr-Platform-DevTools M-27
Labels: -pri-1 -Cr-UI -M-27 Pri-2
 Issue 225641  has been merged into this issue.
This is important because IDEs such as JetBrains PhpStorm offer local debugging of JavaScript running in Chromium. However, as a web developer, I also need to look at the HTML structure of the app sometimes. Losing connection to the debugger and having to backtrack a bit (reload the page) to get it back hurts my productivity.

An acceptable workaround for me would be for only the Scripts tab to break the connection, although I suppose by the time you get there you'd already have addressed the issue that makes the toolbar do it.
 Issue 225271  has been merged into this issue.
It would be nice to get an official statement from the Chrome team on this issue. Why isn't it being fixed? What (if anything) can the community do to raise the priority?

This is forcing developers to choose between external tools (WebStorm, Brackets, Sublime, etc.) and the built-in Chrome Dev Tools. Is that the intention?
I also use an external web debug tool and have this problem where the external debugging gets disconnected once I enable chrome tools.  In firefox, it only disconnects the debug session if i enable the scripts/console tabs.  I can still use the dev web tools to inspect the DOM, which is what I want from chrome as well.

This really should get addressed.

Comment 18 by Deleted ...@, Apr 20 2013

Unfortunatelly I have this problem too. It is very annoying bug.

Comment 19 by, May 10 2013

If you could fix, this would be great for the use of WebStorm's live edit feature, decreasing web development time substantially

Comment 20 by, May 10 2013

@krmckelv  If you are talking about the warning popup that appears, you can use the Canary release version.  Just type in chrome:flags, search for Enable Silent Debugging, and enable this setting.  That will keep the bar from appearing will connected from IntelliJ via Live Edit.

Comment 21 by, May 10 2013

from appearing *when* connected
@dh.LoTan  The issue is that you can't use an external tool to debug and have the Chrome developer tools open at the same time. Though, that's a good tip about how to remove the debugging notice.

Comment 23 by Deleted ...@, May 30 2013

Would be a great time-saver..
This bug has been open more than a year now and it is really important workflow problem. (external tools for debugging, style refreshing, monitoring ... etc can not be used when built in developer tools are open). it hinders substantially developers workflow. can we have it fixed. or at least can somebody comment on when and if it will be fixed.  

Comment 25 by, May 30 2013

It's been assigned. If you do some stalking you can see the developer to whom it is assigned and see what he is up to. Last I checked he was working on other issues. If would be great if that developer would comment on how long he thinks it might be until he got to this issue, but he probably doesn't want to.

FWIW. I tracked down the DevTools PM (Pavel Feldman) at Google I/O and he pledge to address this issue. It sounds like they will be able to add multiple agent support with just a few limitations. Unfortunately, no commitment on schedule, so it could still be awhile.
 Issue 51791  has been merged into this issue.

Comment 28 by, Jun 19 2013

Elements panel will be implemented in WebStorm 7, (It is not yet completed and has bugs, e.g.

Comment 29 by Deleted ...@, Jun 24 2013

any news on this?

Comment 30 by Deleted ...@, Jun 27 2013

I too would love a fix for this, as it affects my development workflow and quite often leaves me a little confused as to which debugger is doing what.

Comment 31 by Deleted ...@, Jun 28 2013

As an WebStorm user i am also affected by this issue. I would love to see a fix!
+1 Would love to see this issue addressed.  Very cumbersome indeed.

Comment 33 by, Jul 21 2013

One of my biggest PITA

Comment 34 by, Jul 22 2013

Here is a handy link to spy on the developer. It would be pretty sweet if he dropped in and said something here!

Chrome needs some kind of feature bounty program. I'm sure this issue would rack up a few dozen $k.

Comment 35 by Deleted ...@, Aug 13 2013

As an WebStorm user i am also affected by this issue too

Comment 36 by Deleted ...@, Aug 29 2013

 an WebStorm user i am also affected by this issue too
This is keeping me from using Chrome as a primary development browser.

Comment 38 by Deleted ...@, Sep 18 2013

I would love to get this fixed as it would aid development immensely.

Comment 39 by Deleted ...@, Sep 18 2013

Please do fix this. Inspecting HTML in the embedded developer tools is very complementary to a remote debugging session - the two should not be mutually exclusive.
I think everyone is dying for this. Someone start a bounty at ;P

Comment 41 by Deleted ...@, Sep 19 2013

please fix this issue! Even WebStorm is referring to this issue, when you start a Javascript debug session when the Web Inspector is open. 

Comment 42 by, Sep 19 2013

Please stop with the "me too" posts, just star it and move on. The issue is understood and assigned, there's no need to explain how useful you think this feature is. The number of stars speaks for itself.

Remember, hundreds of people get notifications whenever this bug gets commented, and being spammed with posts adding nothing new will only drive people to unstar to stop being bugged - thus ultimately hurting the case. 

So, I apologize for the additional noise of this post, and humbly request the comment access to be restricted to members only.

Comment 43 by, Sep 26 2013

please fix!

Comment 44 by Deleted ...@, Sep 29 2013

Please fix!
It's very important bug for all developers, who use JetBrains products. Please fix it.
+1 it would be nice to have this addressed!
Please fix it ! 
Perhaps IE 11 on windows 8.0 ll do better wait until 18 oct 2013  !! 

Comment 48 by Deleted ...@, Oct 28 2013

Please fix!
please fix!
Please fix it

Comment 51 by Deleted ...@, Nov 7 2013

please fix!
pleeaaaaase fix it

Comment 53 Deleted

Comment 54 by Deleted ...@, Nov 8 2013

I am out. This issue is never going to be fixed, and instead of silently starring this issue, people insist on saying "+1"
just hit this with webstorm and surprised this has been open so long.  Please??
Dear Chrome team,
Pleas fix this bug, it's too long
Is the chrome team even reading this? I don't think so...
This is the one thing keeping me from using Chrome instead of Firefox for web-development. If they fear the competition from IntelliJ, this is not the way to handle it.
Stop whining here ><
Fellow devs, if you'd like to ask the Chromium team to address this issue, but don't have anything interesting to say, please just vote for it (star icon to the left of the issue name) and don't leave comments. Otherwise, you fill other voters' inboxes of crap like "please fix this", "C'mon, t's about time!", which belongs to facebook and G+, not an issue tracker. Thanks, and sorry to all other voters for getting you yet another email in your inbox.
Labels: Restrict-AddIssueComment-EditIssue
I'll help with all the emails. ;)  I've restricted comments on this ticket, so from here on out you'll only get updates from the Chrome team.

I plan on posting an update about this issue later this week.

Thanks all for chiming in for your support. As people have mentioned, stars matter a lot, so that's always appreciated. 

Comment 62 by, Nov 19 2013

Labels: Hotlist-DevRel
Blockedon: chromium:403324
Blocking: chromium:449847
Labels: Hotlist-Recharge
This issue likely requires triage.  The current issue owner maybe inactive (i.e. hasn't fixed an issue in the last 30 days).  Thanks for helping out!

Status: Untriaged
 Issue 403324  has been merged into this issue.
Blockedon: -chromium:403324
Labels: Cr-Platform-DevTools-Platform
Status: Assigned
 Issue 673670  has been merged into this issue.
 Issue 733539  has been merged into this issue.
 Issue 749412  has been merged into this issue.
Blocking: chromedriver:483
Status: Fixed (was: Assigned)
I come bearing great news, folks. This bug is now fixed. \o/

 Issue 590878  has the history of work here, but the docs here explain it all:

We very much appreciate your patience and excited to see everything this unlocks.

Sign in to add a comment