Chrome already blocks self signed certs out of the box.
... and then you click the "Advanced" link and click on "Proceed to x.x.x.x (unsafe)"
Not always - some "unsafe" cipher combinations it will simply refuse to load with no workaround. Though you usually only see this on dodgy IoT gadgets out of China/Korea.
I've encountered that a bunch of times. I understand needing to make it look dangerous and deterring people who don't know what they are doing from continuing, but it's silly of Chrome not to offer any way of proceeding for people who do know for certain that they want to.
Unlike FF, Chrome doesn't offer an option for a permanent exception once you click "Proceed to ..."
if you're on a mac, you can add the cert to your keychain and then all your dev sites that operate over *.dev will be fine.
> if you're on a mac
Thanks. I know about that, but I am not on a mac.
I recently set up a self-signed cert for a development site, and Chrome remembered it until I told it to forget it (so I could install a CA-signed cert).
It does, just not on the warning page like ff does. You can install your self-signed cert in the settings panel.