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

Making Safari support ";base64," and ";base64;" would probably be no big deal, especially if 3 other engines support it.

I'd prefer not to allow whitespace in a data URL.  Parsers looking for a URL in unformatted text assume a space is a separator before the next token, not the same URL.

I'd really like to be able to parse a data URL without looking through the base64 encoded bytes twice.  It could get really slow if you have a data URL of many megabytes of base64 data and we must look through it twice to see if it's a base64-encoded data URL.

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