W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2011

[whatwg] Behavior when <script> is removed from DOM

From: Glenn Maynard <glenn@zewt.org>
Date: Fri, 2 Dec 2011 16:28:52 -0500
Message-ID: <CABirCh-Epjh3bOKJg7yEasUVz38jasbH1j8dZOPsCQg+rkGfsA@mail.gmail.com>
On Fri, Dec 2, 2011 at 2:27 PM, Jonas Sicking <jonas at sicking.cc> wrote:

> The main use case for wanting to support scripts getting appears to be
> wanting to abort JSONP loads. Potentially to issue it with new
> parameters. This is a decent use case, but given the racyness
> described above in webkit, it doesn't seem like a reliable technique
> in existing browsers.
> So the questions are:
> 1. Should we keep the spec as it currently stands?
> 2. Are browsers willing to follow the specced behavior?
> 3. Do we want to support the use-case of abourting JSONP loads?

This use case should be covered by this:


I don't actually see the mentioned readyState attribute in
HTMLScriptElement, though.

I think that if aborting script loads is worth supporting (which seems
reasonable), it should be supported in a way that doesn't cause race
conditions (such as the above, or any of the other proposals for delayed
script execution).

Glenn Maynard
Received on Friday, 2 December 2011 13:28:52 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:38 UTC