As of Chrome 52, the UI has changed. When the Developer Tools dialog is open, you select the vertical ellipsis and can then choose the docking position:

[![enter image description here][1]][1]

Select the icon on the left to open the Chrome Developer Tools in a new window: [![multiple windows icon][2]][2]
___________________

## Previously
&lt;strike&gt;**Click and hold** the button next to the close button of the Developer Tool in order to reveal the &quot;Undock into separate window&quot; option.

![enter image description here][3]

Note: A &quot;press&quot; is not enough in that state.&lt;/strike&gt;


  [1]: http://i.stack.imgur.com/rsfGf.png
  [2]: https://i.stack.imgur.com/uggrp.png
  [3]: http://i.stack.imgur.com/u341A.png

[![enter image description here][1]][1]


  [1]: http://i.stack.imgur.com/bSzfh.png

1. click on three dots in the top right -&gt;
2. click on &quot;Undock into separate window&quot; icon

You have to click and hold until the other icon shows up, then slide the mouse down to the icon.

Just type **ctrl+shift+I** in google chrome &amp; you will land in an isolated developer window.

If you need to open the DevTools press **ctrl-shift-i**.


If the DevTools window is already opened you can use the **ctrl-shift-d** shortcut; it switches the window into a detached mode. 

For example in my case the electron application window (Chrome) is really small.

[![enter image description here][1]][1]

It&#39;s not possible to use any other suggestions except the **ctrl-shift-d** shortcut

  [1]: https://i.stack.imgur.com/xitDF.png

`Jenkins` has the `Gerrit` Plugin in place so that when we do check-ins to `Gerrit`, `Jenkins` performs a build and if it succeeds, then the modification in `Gerrit` is verified.  If the build fails then it is not.  My understanding is that this is accomplished through jobs set up in `Jenkins`.  We have now created a new branch (`git`) and I guess I need to clone the existing jobs pointing to the other branch so that this same workflow occurs and builds are performed on every commit.  Can somebody explain how I would clone these jobs? I don&#39;t seem to see a way to do it through the UI nor can I even see a way to list the jobs out through the UI.

How do I clone a job in Jenkins?

I&#39;ve seen in a number of places, including recommendations on this site (https://stackoverflow.com/questions/10376206/preferred-bash-shebang), to use `#!/usr/bin/env bash` in preference to `#!/bin/bash`. I&#39;ve even seen one enterprising individual [suggest using `#!/bin/bash` was *wrong*](http://mywiki.wooledge.org/BashGuide/Practices#Choose_Your_Shell) and bash functionality would be lost by doing so.

All that said, I use bash in a tightly controlled test environment where every drive in circulation is essentially a clone of a single master drive. I understand the portability argument, though it is not necessarily applicable in my case. Is there any other reason to prefer `#!/usr/bin/env bash`over the alternatives and, assuming portability was a concern, is there any reason using it could break functionality?

Why is #!/usr/bin/env bash superior to #!/bin/bash?

When I try to use the Chrome Developer Tools, it seems I can no longer view it in a new window.

Is this a bug or was that really an intended change in an update?

How can we open the Chrome Developer Tools in a new window?

Here&#39;s a screenshot of what I&#39;m talking about.

![enter image description here][1]


  [1]: http://i.stack.imgur.com/vl6Xo.png



How to open the Chrome Developer Tools in a new window?

When I try to use the Chrome Developer Tools, it seems I can no longer view it in a new window.
Is this a bug or was that really an intended change in an update?
How can we open the Chrome Developer Tools in a new window?
Here's a screenshot of what I'm talking about.
<img src="http://i.stack.imgur.com/vl6Xo.png" alt="enter image description here">

I&#39;ve got a browser game and I have recently started adding audio to the game. 

Chrome does not load the whole page and gets stuck at `&quot;91 requests | 8.1 MB transferred&quot;` and does not load any more content; and it even breaks the website in all other tabs, saying `Waiting for available socket`. 

After 5 mins (exactly) the data are loaded. 

![enter image description here][1]

![enter image description here][2]

This does not happen on any other browser.

Removing one MP3 file (the latest added one) fixed the problem, so is it perhaps a data limit problem?


  [1]: http://i.stack.imgur.com/ZutCF.png
  [2]: http://i.stack.imgur.com/FEW4q.png

Chrome hangs after certain amount of data transfered - waiting for available socket

I&#39;m using localhost for development; and I&#39;m directly including jquery from CDN.

It seems that pressing the &quot;Ctrl + R&quot; would force the page to reload, including re-downloading the jquery from CDN.

I want to ask if it&#39;s possible that.. when I refresh, I keep the cache of the jquery from CDN, but clear the cache of my localhost?

NOTE: I know that one thing I can do is to host jquery file locally; I&#39;m just asking to see if there&#39;s a way to bypass that.

Chrome - Disable cache for localhost only?

I&#39;m having an issue where the sourcemaps generated by Webpack using the `inline-source-map` configuration setting are off by one line when I use the Chrome devtools debugger.
Webpack is set up inside a Ruby on Rails application to generate a concatenated, unminified JavaScript file composed of a couple dozen modules.  Most of those modules are ReactJS components, and are parsed by the `jsx` loader.  The output from Webpack is then included in the `application.js` file along with some other JavaScript libraries generated by gems.

When I use `eval-source-map`, there is no problem.  Something about the use of `inline-source-map` causes the line numbers to be thrown off by one.

Inspecting JavaScript that is not a React component still has this issue, so I don&#39;t think it&#39;s related to the use of jsx.

Sourcemaps off by one line in Chrome, with Ruby on Rails, Webpack, and React JS

I&#39;ve experienced some unexpected behavior of Chrome since the newest version:
While in Firefox this Code is working Perfectly fine:

    &lt;a id=&quot;playlist&quot; class=&quot;button&quot; download=&quot;Name.xspf&quot; href=&quot;data:application/octet-stream;base64,PD94ANDSOON&quot; style=&quot;display: inline;&quot;&gt;Download Me&lt;/a&gt;

It isn&#39;t working in Chrome (Simply downloading a file named &quot;Download&quot;), but has worked pretty fine before. What do I have to change that it is working again?

Chrome Download Attribute not working

I have a JavaScript code which save string to the Local storage, the string size is 400000,

    var dataURL = canvas.toDataURL(&quot;image/jpg&quot;).toString();
    localStorage.setItem(&quot;dataURL&quot;, dataURL);

I open the html file from chrome, in one computer its OK in the other computer i get 

&gt; Uncaught QuotaExceededError: Failed to execute &#39;setItem&#39; on
&gt; &#39;Storage&#39;: Setting the value of &#39;dataURL&#39; exceeded the quota.

In this computer I allowed to save string length no more than 100000 chars.
Both computers have the same chrome&#39;s Version 35.0.1916.114 m 
Why?

Setting the value of &#39;dataURL&#39; exceeded the quota

Is there a feature in Google Chrome developer tools that would allow skipping a line without it being executed while debugging, in a similar way that it can be done in Visual Studio?

One workaround I can think of is &#39;live editing&#39; the code by wrapping the line in

    if(false){ //line to be skipped }

But this is not the most convenient workaround that I would have to do after every refresh. **Is there a built-in or faster, better way of doing this?**


Skip line while debugging in Chrome developer tools

I was helping a colleague debug some code today and I noticed a strange behavior with `console.log()` in Google Chrome:

It appears that if you:

1. Create a nested array (e.g., [[345,&quot;test&quot;]])

2. Log the array to the console with `console.log()`.

3. Modify one of the inner array values, then `console.log()` will output the later value -- **not** the values of the array at the time the `console.log()` was executed.

**JavaScript**:

    var test = [[2345235345,&quot;test&quot;]]
    console.log(test);
    test[0][0] = 1111111;
    // outputs: [[1111111,&quot;test&quot;]]
    
    var testb = {};
    testb.test = &quot;test&quot;;
    console.log(testb);
    testb.test = &quot;sdfgsdfg&quot;;
    // outputs: {&quot;testb&quot;:&quot;test&quot;}

    
    var testc = [&quot;test&quot;,&quot;test2&quot;];
    console.log(testc);
    testc[0] = &quot;sdxfsdf&quot;;
    // outputs: [&quot;test&quot;,&quot;test2&quot;]

**[JSFiddle Example][1]**

This behavior does not happen in Firefox.

Also to note, if I stepped through his code line by line in the Chrome debugger, then `console.log()` would output the correct values.

Is there an explanation for this strange phenomenon or is it just a bug with Google Chrome? 

**EDIT:**

I&#39;ve narrowed down the steps to reproduce the inconsistent `console.log()` behavior: 

If you add this script to your page:

    var greetings=[&#39;hi&#39;,&#39;bye&#39;];
    console.log(greetings);
    setTimeout(function(){
        greetings.push(&#39;goodbye&#39;);
    },3000);

and open it in a new window with the Chrome **console window already open**, then the `console.log()` output will be different than if you load the page with the **console window closed**. [Here&#39;s a JSFiddle that demonstrates that](http://jsfiddle.net/markasoftware/kcGkZ/).

In the first case, with the console window already open, `console.log()` will output the current value of the array (i.e., two items). 

In the second case, with the console window initially closed and opened only *after* the page loads, `console.log()` will output the later values of the array (i.e., three items). 

Is this a bug in Google Chrome&#39;s `console.log()` functionality?

  [1]: http://jsfiddle.net/ju3ZV/2/
  [2]: https://vidd.me/dLH

Google Chrome console.log() inconsistency with objects and arrays

Ever since I upgraded to Postman 0.9.6 I can&#39;t replicate user sessions because chrome doesn&#39;t allow postman to get user cookies. However, they have decided to &quot;work around&quot; this issue by created another plugin called Postman Interceptor that routes your postman request and grabs the user cookies. They wrote a blog post about this wonderful tool here: http://blog.getpostman.com/index.php/2014/02/11/postman-v0-9-6-access-cookies-and-restricted-headers-plus-better-testing/

However, I can&#39;t seem to figure out how to get this thing to work. I have been trying for an hour now, and it still won&#39;t see my request as a logged in user

How to use Postman Interceptor

I&#39;m having an error running Chromecast sender in Chrome Incognito or if Chromecast extension is not installed:

    Failed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.js
    Failed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm/cast_sender.js
    Failed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.js
    Failed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js
    Failed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js
    No cast extension found

Google cast sender is trying to send AJAX requests for local &quot;cast_sender.js&quot;. Should this happen or is there a better way to check if Chromecast sender extension exists (not by requesting AJAX request)?

I believe these AJAX requests are a way of asking if Chromecast extension exists. Is there a better way to check if Chromecast extension exists?

Google Chromecast sender error if Chromecast extension is not installed or using incognito

In Chrome DevTools, under Rendering, there&#39;s an option to &quot;Show potential scroll bottlenecks&quot;.

When I enabled this, some `div` elements I have on the screen with `overflow:scroll` show a flag at the top saying &quot;repaints on scroll.&quot;

I can&#39;t find a lot of documentation on this feature, and I don&#39;t know whether it&#39;s something I can actually fix or improve upon, or just a statement of fact - the divs have content, and they do indeed scroll.




Content Type	Original Author	Original Content on Stackoverflow
Question	Abel Callejo	View Question on Stackoverflow
Solution 1 - Google Chrome	Kyle Hale	View Answer on Stackoverflow
Solution 2 - Google Chrome	фымышонок	View Answer on Stackoverflow
Solution 3 - Google Chrome	user1585204	View Answer on Stackoverflow
Solution 4 - Google Chrome	bulkyPanda	View Answer on Stackoverflow
Solution 5 - Google Chrome	Roman Podlinov	View Answer on Stackoverflow

How to open the Chrome Developer Tools in a new window?

Google Chrome Problem Overview

Google Chrome Solutions

Solution 1 - Google Chrome

Previously

Solution 2 - Google Chrome

Solution 3 - Google Chrome

Solution 4 - Google Chrome

Solution 5 - Google Chrome

Why is #!/usr/bin/env bash superior to #!/bin/bash?

How do I clone a job in Jenkins?

Attributions