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

> I am not willing to make WebKit allow spaces in data URLs

I'm afraid that Safari already allows spaces in data URLs in many ways. Here's some stuff I tested in Safari 11 and Technology Preview (results same in both):
https://software.hixie.ch/utilities/js/live-dom-viewer/saved/5758

AFAICT, the model is to find/remove any trailing ";base64", then remove all whitespace and parse that as a MIME type. So even "data: t e x t / h t m l ,<b>foo" works in Safari, but nowhere else. However, the handling of ";base64" seems to allow for no whitespace.

Note that some of [original issues](https://github.com/whatwg/fetch/issues/234#issuecomment-321813664) here were precisely about whitespace. Chrome and Firefox for Android behave differently here, and that was the cause of https://github.com/webcompat/web-bugs/issues/8733. (We have [a project](https://docs.google.com/spreadsheets/d/11OdLcQs6nr3WQgkzu3kSKOPGnneMbZ8Unung8gE6jm8/edit?usp=sharing) to solve some issues like that at its root, by aligning behavior, thus my interest here. I'm not the code owner/decider in Chrome.)

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