Thank you for bringing this to our attention. The developers are aware & currently they are working on this. As a temporary solution, you may wish to use another browser.
Additionally, the lj_releases community will announce when this has been fixed.
You can view lj_releases here.
Thank you for your patience & sorry for the inconvenience.
I imagine running LJ is a bit like being a weatherman - when you get it right, nobody notices (or appears to appreciate it), but get it wrong and they never let you forget.
Hopefully, it won't take too long to fix the problem. In the meantime, I'm looking at this as an opportunity to appreciate how smoothly my LJ runs most of the time (and keeping my fingers crossed that they sort it out soon ).