Re: [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40)

I'm not sure. I think this API might have come from Firefox and they might have had a safelist of MIME types initially they would compare against literally and throw otherwise?

Note that there's other places where we don't allow the full complexity of MIME types, though case-insensitive matching is often done. E.g., `<script type=text/javascript;>` will not execute. For new places we should probably not follow those patterns, but changing these old places is a lot of risk for little-to-no reward.

-- 
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/DOM-Parsing/issues/40#issuecomment-458462693