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

Can the check not be case sensitive?  Is there really existing content like ;Base64?

Skipping no whitespace would keep data URLs to what they ought to have been, but it seems like browsers were more permissive than they should have been and people now rely on it and it's causing compatibility issues and people think we can't go back, so it sounds like I'll have a hard time convincing people here that we should be strict like the original RFC.  We're going to break some content for some browsers no matter what.  I think we shouldn't define the parser to be what annevk, foolip, and I all think is awful.

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