Chrome cookie location


Location to clear cache in Chrome


Ways to make a request in Chrome Dev Tools


You're in a browser, you want to make a server request (say, logout), without having to figure out the headers and such.

// GET
  .then(res => res.json())
fetch('https://toronado.local:8443/api/v1/search', {
  method: 'POST',
  body: JSON.stringify({
    term: 'foo',
    limit: 1
  headers: {
    'Content-type': 'application/json; charset=UTF-8'
.then(res => res.json())
// Imagine the others!

Delete URLs from Chrome Autocomplete on OSX/macOS


On OSX/macosx, it isn't Shift-Delete on a laptop keyboard like all the docs say.

fn + shift + delete

Chrome can't cut and paste without breaking things


"Copying and pasting requires the free Google Drive web app. This lets us access your clipboard so you can cut, copy and paste."

Because THE BROWSER can't? I find this stunning, as even Netscape 1.0 had the ability to cut and paste and it worked *just* *fine.*

Here, let me highlight the text I want to copy, oh, and LOOK! Flower-c works! Hey, I copied it!

WHY I selected the secondary mouse key and thought selecting "Copy URL" was a good thing, I have no idea.

Chrome show IP address


Oddly, Chrome developer tools don't have a "show IP address" option. I say "oddly" because it is a fundamental check that developers do when checking cached items on round-robin DNS servers.

Anyway, via, the ShowIP address plugin / extension gives you the IP address in both IP4 and IP6. They are shown in the bottom right. Whoo.

Unfortunately, this won't help me for the odd edge cache served asset, unless I load only it, which is a little more annoying, but still completely doable.

I prefer Firefox's display of all of the IP address for each asset of the request. Sometimes I'm not working in Firefox.

Regardless, odd problem solved (and I can close that tab! yay!).

Prevent multiple form submits with jQuery in webkit/chrome


Okay, so, you don't want to submit a form twice. While there are server side ways to prevent a form from being accepted twice, it's nice to prevent the need with a little client-side prevention, too. Better user experience, as a bonus.

Using jQuery, you could do this:

    function(e) { 
        $(this).attr('disabled', 'disabled');

The problem with this is that the disabled attribute on the button prevents the form from submitting at all in webkit browsers: Chrome and Safari (ref:

Instead, add a class and check for the class' existence to determine if the form should submit or not.

$(".class-around-each-form form").submit(function(e) {
        if ($(this).hasClass('my-disabled-class')) { e.preventDefault(); return false; }
        return true;

I have a div with a class named .class-around-each-form around each form on a particular page, a quirk specific to my set up. You could use $("form").submit(...) also.

Stupid simple and frustrating if you didn't realize its need, or didn't test on all the browsers.