Is this still a problem for you? I was not able to duplicate this bug on firefox 1.0.5 or 2.0b1 or 2.0b2
Is this still a problem for you? I was not able to duplicate this bug on firefox 1.0.5 or 2.0b1 or 2.0b2