Updating to 1.0.8 hasn’t fixed this error, as I use Pale Moon (a Firefox fork), rather than IE, as the update was aimed at.
Hmm, I didn’t realize some of the problems were coming from WP itself. That’s unfortunate. Good to hear you’re doing your best to work around that anyway, though.
Sure enough, that did the trick. Thanks!
