On Sat, 28 May 2011, John J. Barton wrote:
To allow optional JavaScript download, some widely used JavaScript
libraries, such as jQuery and requireJS, use script elements added to
the document dynamically by JavaScript. (Of course this feature is also
used by applications directly as
Hi John,
This event is actually already speced, see #14 fire a simple event
named error at the element in:
http://www.whatwg.org/specs/web-apps/current-work/#prepare-a-script
(and the onerror attribute is valid for all elements)
Best regards
Mike Wilson
John J. Barton wrote:
To allow
John J. Barton wrote:
Step 14 is unclear or incomplete however:
If the src
http://www.whatwg.org/specs/web-apps/current-work/#attr-script-src
attribute's value is the empty string or if it could not be resolved,...
Does this mean the error handler will be called in the case of 4XX, 5XX, and
Mike Wilson wrote:
John J. Barton wrote:
Step 14 is unclear or incomplete however:
If the src
http://www.whatwg.org/specs/web-apps/current-work/#attr-script-src
attribute's value is the empty string or if it could not be resolved,...
Does this mean the error handler will be called in the case
On 5/29/11 11:08 AM, John J. Barton wrote:
(I've not seen a for attribute on a script element. Is there any
documentation on what it does?)
http://www.idocs.com/tags/scripts/_SCRIPT_FOR.html sort of describes it.
So does MSDN if you read carefully enough, but the latter's description
is
To allow optional JavaScript download, some widely used JavaScript
libraries, such as jQuery and requireJS, use script elements added to
the document dynamically by JavaScript. (Of course this feature is also
used by applications directly as well). For normal deployment this
approach works
