On Apr 19, 4:25 pm, Alex Wallace <alexmlwall...@gmail.com> wrote:
> > Because of a third-party control for ASP.NET we're using, under certain
> > conditions, the generated HTML has this little gem shortly after the opening
> > <form> tag:
> >     <AsyncException>Error occured during AsyncInvocation.</AsyncException>

> Internet Explorer doesn't know how to handle abnormal tag names, but perhaps
> you could use a shim to "alert" IE that there are "elements" named
> AsyncException. Try adding:
>   document.createElement("AsyncException");
> somewhere very early on in the script flow.

Okay, but how could that help in hiding the message "Error occured
during AsyncInvocation" that always appears because of the way
browswers have displayed text in unknown elements since day one?

> The best option, of course, is to prevent it from being output on the
> backend, but it sounds like all available routes have already been
> exhausted.

Unfortunately yes.



You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to