Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)

I agree.  Actually, it seems very bad to me.

I still suspect we won't see much breakage here (I mean, really, who uses that character?), but it does mean this has the potential to break pages.  I'm much less gung ho about removing support for it now, but I still think doing so is best for the long term health of the platform, if we can manage it.  I've made enough changes to Chrome's header parsing (One more is in the pipeline) in this version that I'm not comfortable making more until the current set has made it to stable or at least been on beta for a while, but we are going to have to change Chrome's behavior here, regardless, at some point.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/818#issuecomment-434356059