- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Mar 2014 13:28:07 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21275 --- Comment #28 from Gordon P. Hemsley <me@gphemsley.org> --- (In reply to Anne from comment #19) > No it's not. All kinds of things are different around script execution and > such. The HTML we have is something you load in a browsing context. This is > something else. Similarly HTML loaded through XMLHttpRequest has > restrictions on encodings (though not enough). I agree with Anne's assessment that this would be a new "import" context which would require its own entry in the Context-specific sniffing section of mimesniff (akin to the style context, among others): http://mimesniff.spec.whatwg.org/#context-specific-sniffing As such, we can enforce any stricter restrictions on it that we want, and I think that would include requiring utf-8 and an appropriate MIME type. (I assume this would be specified through the Content-Type header, but Anne may have other ideas.) One concern of mine regarding the MIME type is XHTML: These imports seem to be available to XHTML documents as well as HTML documents, so I would think that the imported documents would also be allowed to be XHTML documents. This would mean, in addition to allowing "text/html", we would also need to allow an(y) XML type. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 18 March 2014 13:28:08 UTC