- From: <bugzilla@jessica.w3.org>
- Date: Thu, 08 May 2014 22:44:34 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25567 --- Comment #7 from Morrita Hajime <morrita@google.com> --- (In reply to Anne from comment #6) > My apologies, you're correct. That needs patching somehow. > > It's also unclear to me why HTML imports does not use the "obtain the > resource" algorithm from HTML to get to the bits. It seems that could be > reused. Unfortunately the "obtaining..." algorithm cannot be used for imports as is because: - It does have to handle de-dup. - Its CORS behavior is different. For imports, "cross-origin request" should be always performed. In other words, it needs different @crossorigin default, that is Anonymous, instead of null. Any CORS-unaware HTML shouldn't be loaded through import system. I clarified it needs different fetch algorithm [1]. It wasn't that obvious before. [1] https://github.com/w3c/webcomponents/commit/85ad4cb477af8176be47a9c59b302e2a94734703 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 8 May 2014 22:44:36 UTC