If this is the same issue as was occurring in Firefox 3.0, then it has now been fixed.