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

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

From: Yehuda Katz <wycats@gmail.com>
Date: Sat, 3 Dec 2011 18:24:26 -0800
Message-ID: <CAMFeDTVPaP6SgCL9dEWMN8v7Uoqt6_Dqv0UWwLTn-+39hg=OEg@mail.gmail.com>
Yehuda Katz
(ph) 718.877.1325


On Fri, Dec 2, 2011 at 11:30 AM, Tab Atkins Jr. <jackalmage at gmail.com>wrote:

> 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.
>

Cross-domain XHR *can* solve this use case, but the fact is that CORS is
harder to implement JSONP, and so we continue to have a large number of web
APIs that support JSONP but not CORS. Unfortunately, I do not forsee this
changing in the near future.


>
> ~TJ
>
Received on Saturday, 3 December 2011 18:24:26 UTC

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