Thank you for the response... Indeed I agree that this is a browser limitation - but as with many things (styling for example) we must anticipate the limitations of the browser and provide a working solution for any browser.
I have done some research on this error and found out that explorer has a built-in limit for the number of statements it can execute from a parent call - 5 Million. In addition, it has a 10 second timeout for loops.
In my case, I have made sure that I don't have any potentially offensive code that could be the source of the problem, and think that indeed the issue is within the code of the rotator in coverflow mode.
I noticed something interesting...
If one loads the page, and does not move the rotator to any item other than its initial item, and doesn't touch anything - the error is avoided.
if one then moves the rotator to the next item, the error pops up.
if one chooses "no" in the error popup, then it will work for ~3 seconds, and then pop up again. Repeating this process, the error will pop up three times total.
After the third error, the page works fine....
I find this interesting for a couple of reasons.
1) It would appear that if the error pops up 3 times, there might be 15 million executed statements?! that seems a bit steep to me...
2) You mentioned that the rotator must load all of the images in order to make some calculations... however, this shows that even if all of the images are loaded entirely (ie, we wait for a minute after page load) the error still occurrs... telling us that this isn't really a timing issue, but rather a # of statements executed issue?
Could you please educate me on what happens differently the very first time the rotator moves, versus the second time? clearly, the first time the rotator moves, much more code is executed...
also, i found this article:
which, perhaps, something of the sort could be implemented in the rotator's client library?
This is a pretty big issue for us... we just bought the telerik controls for a website we have built, but we now cannot go live because of these issues with IE compatability.
We just found that we get the same issue on a separate page (in certain cases which we can't figure out yet) which uses a radgrid and radtreeview...
I really appreciate any help you guys can offer. thanks.