P
Paul K
There appears to be a bug in the Windows version of IE6
with loading images. I've reproduced this on several
computers running either Windows ME and 2000 (yes, even
computers with no firewall or antivirus software
installed). To reproduce the bug, simply take a small
image, and display it 100 or so times on a simple web page
saved to your local drive. When displayed in IE6, it comes
up fine -- even if you refresh numerous times.
Then make a copy of that file and add a simple
<script language="javascript"></script>
line to the head block. No need to add any code to the
javascript block, unless you want to. Now display this
file in IE, and if the image appears the first time, keep
refreshing. The images often (if not always) disappear. It
appears the more often an image appears on the page, the
more often the bug presents itself.
Note that if you right-click the image placeholder and
select Show Picture, the image always appears. And yes, I
have seen KB article 283807 -- none of the suggested
solutions solve this problem.
Can anyone else confirm this as a bug and/or provide a
workaround? Thanks.
with loading images. I've reproduced this on several
computers running either Windows ME and 2000 (yes, even
computers with no firewall or antivirus software
installed). To reproduce the bug, simply take a small
image, and display it 100 or so times on a simple web page
saved to your local drive. When displayed in IE6, it comes
up fine -- even if you refresh numerous times.
Then make a copy of that file and add a simple
<script language="javascript"></script>
line to the head block. No need to add any code to the
javascript block, unless you want to. Now display this
file in IE, and if the image appears the first time, keep
refreshing. The images often (if not always) disappear. It
appears the more often an image appears on the page, the
more often the bug presents itself.
Note that if you right-click the image placeholder and
select Show Picture, the image always appears. And yes, I
have seen KB article 283807 -- none of the suggested
solutions solve this problem.
Can anyone else confirm this as a bug and/or provide a
workaround? Thanks.