This problem is already confirmed and workarounds are identified, however we need to know if it is reproducible with firefox 3.1 Beta 2, can someone test it?
This problem is already confirmed and workarounds are identified, however we need to know if it is reproducible with firefox 3.1 Beta 2, can someone test it?