The error message in your screenshot says "invalid key", not "untrusted certificate". If the browser can't do the encryption, how do you expect it to continue?
I'm just an average user that no one cares about, but if you dare read the comments on that blog, it seems this bug and the slow response to it pissed off a lot of corporate IT folk whose self-signed apps they borked.