beefeather / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
Other
0 stars 0 forks source link

Inspector does not work when debugger is connected #28

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Google Chrome version: 4.1.249.1045
SDK + Eclipse Debugger version(s): 3.2.1, DevTools from current SVN
OS + version:

What steps will reproduce the problem?
1. Run Chrome
2. Connect debugger
3. Press Ctrl+Shift+I

What is the expected result?
Nothing happens

What happens instead?
Web inspector window should appear

Please provide any additional information below. If possible, attach a
(reduced) test-case.

I understand this is deliberate and has its reason. But it would be much 
easier to understand if there was some pop-up message that explains that 
debugger should be disconnected.

Original issue reported on code.google.com by eostrouk...@gmail.com on 1 Apr 2010 at 9:45

GoogleCodeExporter commented 8 years ago
Eclipse is working as an alternate debugger front-end in this case. I think we 
should bring Eclipse window to 
front upon Ctrl+Shift+I. This would be universal and inline with other 
potential alternate front-ends. Would also 
give user enough clue on why he does not see the original dev tools window.

Original comment by pfeld...@chromium.org on 2 Apr 2010 at 5:08

GoogleCodeExporter commented 8 years ago
The problem we are having is that the user will want both Web Inspector and IDE 
debugger - web inspector has several important features like resource monitor 
(that is 
extremely useful to monitor AJAX requests during the debug) and DOM inspector.

Original comment by eostrouk...@gmail.com on 2 Apr 2010 at 4:37

GoogleCodeExporter commented 8 years ago
The use case is admittedly rightful. However there are some technical 
difficulties (on Chrome side) with implementing this.
The issue remains open and worked on.

Original comment by peter.ry...@gmail.com on 3 Aug 2010 at 9:38

GoogleCodeExporter commented 8 years ago
Related bug in Chrome database:
http://code.google.com/p/chromium/issues/detail?id=51791

Original comment by peter.ry...@gmail.com on 11 Aug 2010 at 2:29