Did you see this on firefox 2.0.0.4 or 2.0.0.5? is it possible that you upgraded firefox to 2.0.0.5 and it fixed after that?
Are you able to reproduce this using something other than firefox or something other than a gecko browser like konqueror or like gnumeric. as descibed in gnomes upstream bug you listed.
Did you see this on firefox 2.0.0.4 or 2.0.0.5? is it possible that you upgraded firefox to 2.0.0.5 and it fixed after that?
Are you able to reproduce this using something other than firefox or something other than a gecko browser like konqueror or like gnumeric. as descibed in gnomes upstream bug you listed.