After conducting tests on embedded flash widgets, it has come to my attention that the onerror event, when used with an object tag, may not be compatible across all browsers. However, we are noticing that Internet Explorer users are encountering this handler quite frequently.
I am aware that this handler is typically triggered when a SWF file fails to load due to reasons such as a 404 error, 410 error, or network issue. Are there any other circumstances in which this event might be called?
Considering these widgets are not created by us, could it be possible for an onerror event to be initiated from within the embedded flash file? This could explain why we are observing this behavior.
Additionally, is there a way to gather more information about the cause of the onerror event when it occurs?
In summary, our main concern is whether we can confidently assume that if an onerror event is triggered from an object tag, it indicates a failed SWF loading process, allowing us to attempt reloading it from a different URL. We want to avoid unnecessarily reloading the SWF if onerror was activated for a reason unrelated to loading failure.
Some extra details:
We are utilizing the Flash Satay method for embedding flash and simply attaching the onerror attribute to the object tag like so:
<object .... onerror="ourAjaxLogFunction()">
Thank you for your assistance.