> I think this is just a result of some of your images not yet being > downloaded to the browser when Cycle transitions them in. You can > either add images dynamically (see the 'add' demos on the Cycle page) > or wait until the window 'load' event fires (instead of using the > 'ready' event) to start Cycle.
I changed the page to hide the images until the window load is complete, and then I am triggering Cycle. That seems to be working fine. Thanks for the suggestion! However, I still don't quite understand the previous behavior. The images were not missing just until they were downloaded. They were never displayed, even long after the page was loaded and the images had been cycled through multiple times. I agree that the problem seems to be that the browser does not have a copy of the images, but I can't explain why. Is there something about starting Cycle before the images are downloaded that causes the browser to stop downloading them? Is Cycle actually removing the images from the DOM rather than just hiding them? If so, that would explain what I am seeing. TNTitan
