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

> otherwise you could not have a MIME type with a comma in it.

That's not allowed anyway, per the syntax for MIME types defined in <https://tools.ietf.org/html/rfc2045#section-5.1>.  At least for the type itself; MIME parameters are a separate issue....

>They don't normalize text/pl%61in to text/plain

Hmm.  In my testing via the URL bar they did.  And `<iframe src="data:text/pl%61in,Some text"></iframe>` rendered as plaintext.  But you're right, that the latter just seems like "no valid type" error recovery, and who knows what browsers do with URL bar input.

> I would prefer it not working [the busted base64 thing]

I think I would too, if we can figure out a simple way to spec that...

> I think we should either require ;base64 to be the actual last thing as per the RFC or allow it to occur anywhere. Some kind of mix seems rather confusing.

I think the idea behind the Firefox impl is that people might add random garbage to the end of the RFC-specified bits.  Might be worth checking the history of why the parsing there is so loose.

That said, does Safari basically enforce ";base64" being the very last thing?  Just trying to feel out the compat constraints here.



-- 
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-330229846