http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q818506
that may be part of the problem, seems to only manifest itself in XP for me
on IE6, and has been a real pain in the ass to track down. also, I think
these bugs are all related:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=O7WqnJZ4
CHA.2308%40TK2MSFTNGP11.phx.gbl&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3
DUTF-8%26oe%3DUTF-8%26q%3Dxp%2Binternet%2Bexplorer%2Bjavascript%2Bimage%2Bso
cket%26meta%3Dgroup%253Dmicrosoft.public.windows.*
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=18ca5147
..0305160743.1dd0b478%40posting.google.com&rnum=3&prev=/groups%3Fhl%3Den%26lr
%3D%26ie%3DUTF-8%26oe%3DUTF-8%26q%3Dxp%2Binternet%2Bexplorer%2Bjavascript%2B
image%2Bgroup%253Amicrosoft.public.*%26meta%3Dgroup%253Dmicrosoft.public.*
plus I have recreted teh situation on my own XP client tests... if you want
my test file, I'll send it to you. I really need this fixed for some
installs that i have that use the browser as a deployment method in an
application that has over 20k lines of js in it, so you can understand how
important it is for me to find/share as much information about this bug as
possible...
JP