This is fixed in 3.0 as i recall, not sure why upstream bug didnt mrak bug as resolved. Firefox 2.0 will never see this fix.
This is fixed in 3.0 as i recall, not sure why upstream bug didnt mrak bug as resolved. Firefox 2.0 will never see this fix.