[Bug 21226] [Imports]: Components fetching should always use CORS.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21226

Morrita Hajime <morrita@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |morrita@google.com
         Resolution|---                         |FIXED

--- Comment #7 from Morrita Hajime <morrita@google.com> ---
(In reply to Anne from comment #6)
> The <track> element works like that, yes. No real opinion on what is better,
> but some consistency throughout would be good.

For <track>, it makes sense to load it but not to expose the detail through
API. So having @crossorigin (on its parent <media>) makes sense. However for
imports, it doesn't make sense to do that: Unlike movie subtitles,
API-invisible imports aren't useful at all.

Theoretically we could possibly have @crossorigin for imports so that the
author can make requests with credentials. But I don't see any usecase for
that.
In contrast, not having @crossdomain makes the usage easier/simpler. If we
introduce @crossorigin, people needs to give @crossorigin all the time once
they want it CDN-aware, which is sad. I prefer to have better default than to
just make the orange consistent to apples.

I'm closing this for now. Feel free to reopen this to continue conversation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 19 September 2013 01:55:42 UTC