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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 2 Dec 2011 11:30:43 -0800
Message-ID: <CAAWBYDCbMuiN1hyuXE0atyYA54inJwxkY_N_naaXB6Dtfx3zJA@mail.gmail.com>
On Fri, Dec 2, 2011 at 11:27 AM, 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.

If it's unreliable *and* no sites appear to break with the proper
behavior, we shouldn't care about this use-case, since cross-domain
XHR solves it properly.

Received on Friday, 2 December 2011 11:30:43 UTC

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