Surely that’s a bug for the Chrome folks, not Less Wrong. It works fine in the stable release of Chrome.
We’ll keep an eye on this. We won’t be chasing fixes for developer releases but if the problem persists it will be fixed.
I assumed it was something with the codebase here because one day it was working fine, and the next it wasn’t, without any changes to my browser. shrug
Surely that’s a bug for the Chrome folks, not Less Wrong. It works fine in the stable release of Chrome.
We’ll keep an eye on this. We won’t be chasing fixes for developer releases but if the problem persists it will be fixed.
I assumed it was something with the codebase here because one day it was working fine, and the next it wasn’t, without any changes to my browser. shrug