<link rel=prefetch> does that for you. On Apr 17, 2015 7:08 PM, "Glen Huang" <curvedm...@gmail.com> wrote:
> One benefit is that browsers can start downloading it asap, instead of > waiting util the fetch code is executed (which could itself be in a > separate file). > > On Apr 18, 2015, at 8:41 AM, Elliott Sprehn <espr...@chromium.org> wrote: > > > > On Fri, Apr 17, 2015 at 6:33 AM, Glen Huang <curvedm...@gmail.com> wrote: > >> Basic feature like this shouldn't rely on a custom solution. However, it >> does mean that if browsers implement this, it's easily polyfillable. >> > > What does this get you over fetch() ? Imports run scripts and enforce > ordering an deduplication. Importing JSON doesn't really make much sense. > > >> On Apr 17, 2015, at 9:23 PM, Wilson Page <wilsonp...@me.com> wrote: >> >> Sounds like something you could write yourself with a custom-elements. >> Yay extensible web :) >> >> On Fri, Apr 17, 2015 at 1:32 PM, Matthew Robb <matthewwr...@gmail.com> >> wrote: >> >>> I like the idea of this. It reminds me of polymer's core-ajax component. >>> On Apr 16, 2015 11:39 PM, "Glen Huang" <curvedm...@gmail.com> wrote: >>> >>>> Inspired by HTML imports, can we add JSON imports too? >>>> >>>> ```html >>>> <script type="application/json" src="foo.json" id="foo"></script> >>>> <script type="application/json" id="bar"> >>>> { "foo": "bar" } >>>> </script> >>>> ``` >>>> >>>> ```js >>>> document.getElementById("foo").json // or whatever >>>> document.getElementById("bar").json >>>> ``` >>>> >>>> >> >> > >