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

@mikewest, yes, I think that compat-wise, we could probably get away with it. It just seems like pointless breakage to me that we can easily spare people from. Note that there's only one of the below that wouldn't be treated as base64:
* `data:text/plain;base64,WA` (no whitespace)
* `data:text/plain ;base64,WA` (whitespace before semicolon)
* `data:text/plain; base64,WA` (whitespace after semicolon)
* `data:text/plain;base64 ,WA` (whitespace before comma)

I'd struggle to explain why it makes sense to web developers.

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