Yes, see comment #79 on the mozilla bug report. Looks like the fix will be rolled into Firefox 3.0.5. I'm looking forward to it too.
Yes, see comment #79 on the mozilla bug report. Looks like the fix will be rolled into Firefox 3.0.5. I'm looking forward to it too.