Javascript errors happen all the time due to weird browsing behavior and usually go unnoticed by typical users (unless of course it's being caused by your actual code). The fact that the error pops up in an alert window is a debugging feature of the Development environment in Rails. In other words, when your site is in Production mode on the server, the error should not trigger an alert window at all, and the error should generally go unnoticed by the user. And if they're clicking to another page, then the error should have no effect on their browsing experience.
Unless of course you are getting these alerts in production mode, in which case that's a whole other situation. -Steve On Jul 12, 3:06 am, rockrep <[email protected]> wrote: > We have an issue where we are using RJS templates to render the > results of Ajax calls. Everything works fine so long as the user > waits for the render to occur. However, if the user initiates the > request and the RJS template is still in the process of rendering, but > hasn't completed, and the user clicks a different link, then we get a > Javascript alert popup "Unexpected Server Error" for each line of RJS > that has not yet completed. There is no stacktrace in the > development (or production) log. Once the alert(s) are cleared, the > secondary request completes fine. > > What is best practice for guarding against this situation, or at a > minimum prevent the alert popup? We tried putting begin/rescue > blocks around the RJS but that did not seem to help. > > Any pointers appreciated. > > Thanks, > > Michale --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
