On a web app ive got a login page that is the default page of the program. If youve got a valid cookie set then it never shows any controls it just validates that cookie data and then does a show for the main page of the app. If the cookie is not valid or not there then it shows its login controls for you to enter the password. For the longest time there was a very annoying bug that I couldnt sort out that if you had a saved cookie it would work perfectly, but if you had to enter the password then youd get a page full of javascript errors when trying to load the main page. maybe 4 out of 5 times it would fail to load at all but the 5th time you could dismiss the javascript error and the rest of the page would seem to be working, at least enough to save its logged in cookie to avoid errors in the future.
Today that reached the top of my list again and it turns out to be a problem with the animation.complete event. I was using an animation to fade out the login controls to signify that something worked and then in the completion event I was doing a .show for the main page. Thats what caused the error. If I did the show directly where I started the animation then it worked perfectly. Also if I created a web timer with its mode set to 1 in the animation.complete event and let the timer event show the new page that also worked fine.
Im not sure even how to open a bug report for this, but there is definitely something different about the timing that the animation.complete event calls into vs all the other controls. If youre having trouble showing a new page after an animation on a page then this is likely the issue. I cant seem to duplicate it in a simple app, its only when the page youre showing starts to be complex and has a lot of controls that it shows up as a problem.