Artem: Please read at least the final few comments before posting on a bug.... If you had, you'd see that this bug already has a patch that is targeted to be in a release very soon. (As mentioned multiple times above, "me too" comments are un-helpful at this point, and they only serve to make this bug longer and harder to read.)
To make this comment slightly more useful, I'll add a relevant update -- Firefox 3.0.10 has actually been converted into a quick security release[1] with only ~2 patches. So the fix for this bug here won't actually arrive until Firefox 3.0.11 (which nonetheless should still be out soon).
Artem: Please read at least the final few comments before posting on a bug.... If you had, you'd see that this bug already has a patch that is targeted to be in a release very soon. (As mentioned multiple times above, "me too" comments are un-helpful at this point, and they only serve to make this bug longer and harder to read.)
To make this comment slightly more useful, I'll add a relevant update -- Firefox 3.0.10 has actually been converted into a quick security release[1] with only ~2 patches. So the fix for this bug here won't actually arrive until Firefox 3.0.11 (which nonetheless should still be out soon).
[1] source: https:/ /wiki.mozilla. org/Releases/ Firefox_ 3.0.10/ Test_Plan