Today I got an update of FF to 2.0.0.1 and with some other updates related to FF it now seems like this annoying bug is gone.
Today I got an update of FF to 2.0.0.1 and with some other updates related to FF it now seems like this annoying bug is gone.