Separate the JS Console view as a separate window in Chrome Developers Tools
up vote
0
down vote
favorite
In the age of multiple monitors I'd love to split the Console tab in Chrome Developers tools as a separate window, is there any way to do so?
I'll settle for being able to launch two instances of the Chrome Developer Tools as well.
And yes I'm aware of the ESC keyboard to open the drawer :)
google-chrome-devtools
add a comment |
up vote
0
down vote
favorite
In the age of multiple monitors I'd love to split the Console tab in Chrome Developers tools as a separate window, is there any way to do so?
I'll settle for being able to launch two instances of the Chrome Developer Tools as well.
And yes I'm aware of the ESC keyboard to open the drawer :)
google-chrome-devtools
1
No such built-in feature, but two workarounds exist since Chrome supports several simultaneous debuggers: 1) run chrome with command l ine--remote-debugging-port=9999
then go tolocalhost:9999
and open a second web-based devtools 2) attach to the tab via another extension or maybe externally (Puppeteer, Selenium, etc).
– wOxxOm
Nov 9 at 4:28
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In the age of multiple monitors I'd love to split the Console tab in Chrome Developers tools as a separate window, is there any way to do so?
I'll settle for being able to launch two instances of the Chrome Developer Tools as well.
And yes I'm aware of the ESC keyboard to open the drawer :)
google-chrome-devtools
In the age of multiple monitors I'd love to split the Console tab in Chrome Developers tools as a separate window, is there any way to do so?
I'll settle for being able to launch two instances of the Chrome Developer Tools as well.
And yes I'm aware of the ESC keyboard to open the drawer :)
google-chrome-devtools
google-chrome-devtools
asked Nov 9 at 4:23
Daniel Sokolowski
7,73724643
7,73724643
1
No such built-in feature, but two workarounds exist since Chrome supports several simultaneous debuggers: 1) run chrome with command l ine--remote-debugging-port=9999
then go tolocalhost:9999
and open a second web-based devtools 2) attach to the tab via another extension or maybe externally (Puppeteer, Selenium, etc).
– wOxxOm
Nov 9 at 4:28
add a comment |
1
No such built-in feature, but two workarounds exist since Chrome supports several simultaneous debuggers: 1) run chrome with command l ine--remote-debugging-port=9999
then go tolocalhost:9999
and open a second web-based devtools 2) attach to the tab via another extension or maybe externally (Puppeteer, Selenium, etc).
– wOxxOm
Nov 9 at 4:28
1
1
No such built-in feature, but two workarounds exist since Chrome supports several simultaneous debuggers: 1) run chrome with command l ine
--remote-debugging-port=9999
then go to localhost:9999
and open a second web-based devtools 2) attach to the tab via another extension or maybe externally (Puppeteer, Selenium, etc).– wOxxOm
Nov 9 at 4:28
No such built-in feature, but two workarounds exist since Chrome supports several simultaneous debuggers: 1) run chrome with command l ine
--remote-debugging-port=9999
then go to localhost:9999
and open a second web-based devtools 2) attach to the tab via another extension or maybe externally (Puppeteer, Selenium, etc).– wOxxOm
Nov 9 at 4:28
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53219845%2fseparate-the-js-console-view-as-a-separate-window-in-chrome-developers-tools%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
No such built-in feature, but two workarounds exist since Chrome supports several simultaneous debuggers: 1) run chrome with command l ine
--remote-debugging-port=9999
then go tolocalhost:9999
and open a second web-based devtools 2) attach to the tab via another extension or maybe externally (Puppeteer, Selenium, etc).– wOxxOm
Nov 9 at 4:28