Sorry about that! Firefox is currently on version 1.3.8, which is affected by this bug. We’ve fixed the issue in the next version and are still going through the Firefox release process. Thanks for your patience!