We've found the issue - it has to do with a busted workaround for the Firefox scrolling issue. Apparently our workaround for a bug in Firefox exposed another problem. We've repaired the issue, and it will be out in the next service release later this week.