T
Tony B
We're having issues with multiple frames and the progress
indicator on the status bar: It will post form data,
response will complete, and then the progress indicator
starts over and begins moving slowly (taking up to 25
minutes to complete). Nothing is running in the browser
window (used "debugger" to verify). No spyware or 3rd
party extensions.
Reference KB article #293373 - which does NOT mention IE6.
Reference post on google groups:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-
8&threadm=191115aa.0402160307.7079b5ab%
40posting.google.com&rnum=7&prev=/groups%3Fhl%3Den%26lr%3D%
26ie%3DISO-8859-1%26q%3DProgress%26meta%3Dgroup%
3Dmicrosoft.public.internet.explorer.ieak
I can kludge the code so that the form-post is done in
a "window.setTimeout(blah.submit(), 100)", which reduces
the frequency of this problem. Due to the size of this
application, this kludge is not an acceptable solution.
Does anyone have any advice or insight into "when this
will be fixed?" It's a major annoyance for our user group.
Thanks in advance,
Tony
P.S. I can replicate this problem by browsing MSDN - it
occurs at seemingly random times.
indicator on the status bar: It will post form data,
response will complete, and then the progress indicator
starts over and begins moving slowly (taking up to 25
minutes to complete). Nothing is running in the browser
window (used "debugger" to verify). No spyware or 3rd
party extensions.
Reference KB article #293373 - which does NOT mention IE6.
Reference post on google groups:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-
8&threadm=191115aa.0402160307.7079b5ab%
40posting.google.com&rnum=7&prev=/groups%3Fhl%3Den%26lr%3D%
26ie%3DISO-8859-1%26q%3DProgress%26meta%3Dgroup%
3Dmicrosoft.public.internet.explorer.ieak
I can kludge the code so that the form-post is done in
a "window.setTimeout(blah.submit(), 100)", which reduces
the frequency of this problem. Due to the size of this
application, this kludge is not an acceptable solution.
Does anyone have any advice or insight into "when this
will be fixed?" It's a major annoyance for our user group.
Thanks in advance,
Tony
P.S. I can replicate this problem by browsing MSDN - it
occurs at seemingly random times.