Re: [w3c/webcomponents] JSON "modules" (#770)

> Perhaps you missed that this effort is about defining the (default) loader for the browser. So yes, some things can be done through a more complicated setup, but it'd be nice if in the future that could be avoided altogether.

See my edited post

> It's much more reliable to handle it at server side, you know, for browser compatibility, unless browser send a special Accept header to indicate its support.
>
> The same problem applies to <script type=module>. Browser still sends `Accept: */*` for <script type=module> so <script nomodule> exists

But you can't assume `./data.json` is a json file. Browsers never guess file type based on its extension. That's how browsers work

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/770#issuecomment-433979919