W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: JSON imports?

From: Elliott Sprehn <esprehn@chromium.org>
Date: Fri, 17 Apr 2015 17:41:40 -0700
Message-ID: <CAO9Q3i+2_71SG57nAgh7g9gNFcaPwjnPrbrFosLBRGhKFP2P5g@mail.gmail.com>
To: Glen Huang <curvedmark@gmail.com>
Cc: Wilson Page <wilsonpage@me.com>, Matthew Robb <matthewwrobb@gmail.com>, public-webapps <public-webapps@w3.org>
On Fri, Apr 17, 2015 at 6:33 AM, Glen Huang <curvedmark@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 <wilsonpage@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 <matthewwrobb@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" <curvedmark@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
>>> ```
>>>
>>>
>
>
Received on Saturday, 18 April 2015 00:42:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC