[whatwg] script element onerror event
John J. Barton
johnjbarton at johnjbarton.com
Sat May 28 20:48:03 PDT 2011
libraries, such as jQuery and requireJS, use script elements added to
used by applications directly as well). For normal deployment this
approach works well in practice. At development time however, or in the
presence of network or server problems, the approach gives poor error
recovery information. Fundamentally the problem is that the insertion
mechanism has no error return path.
The script element does support one event, 'onload' which fires after
the script has finished loading. I suggest the addition of one new
event, 'onerror', which fires in every other case. For examples, a
but not onload. On the other hand, a runtime error for the
outer-function of the script element would trigger onload (I guess), but
the developer can handle this with try/catch.
Very long load times would still have poor error recovery information,
but developers could implement UI to signal "loading..." once they know
they will get some update event eventually.
More information about the whatwg