I just tested on a machine that still has IE 6.0.2800.1106 on it on the standard client and couldn't reproduce this. I am still on 6.0.0 though, will be preforming the update tonight and will test again then.
I would suggest the obvious of clearing the browser cache in the meantime, but you have probably already tried that
