FWIW, the upstream patch (in Mozilla's bug tracker) has just recently landed in the repository that Firefox 3.0 is built from -- assuming all goes well, that means this should be fixed in Firefox 3.0.10. (It also should be fixed in Firefox 3.5b4)
FWIW, the upstream patch (in Mozilla's bug tracker) has just recently landed in the repository that Firefox 3.0 is built from -- assuming all goes well, that means this should be fixed in Firefox 3.0.10. (It also should be fixed in Firefox 3.5b4)