Re: [whatwg/fetch] Define data: URLs (#579)

> Making the MIME type parser aware of the base64 bit seems rather ugly, especially as it's not a valid MIME type parameter and it's not applicable in any other context taking a MIME type.

Yes, it's rather ugly. But when 3/4 engines support something and it's so easy to find examples in the wild, I think it's safe assumption that *something* will break, and even if it would work out in the end, it seems like pointless breakage.

I think the behavior should be *as if* the MIME parser looked for this token, but we can do it outside of it as well.

How about we split the string by semicolons, trim whitespace (the same kind that the MIME parser would skip) of the resulting strings, and check if any string is the token "base64"?

-- 
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/579#issuecomment-355658126