[whatwg/url] unicode fragments (#150)

Right now there is a note: "Unfortunately not using percent-encoding is intentional as implementations with majority market share exhibit this behavior."

I think we should change "Append c to url’s fragment." to at least "If url’s scheme is a special scheme, append c to url’s fragment.  Otherwise, append the result of running UTF-8 percent encode with the simple encode set on c" or something similar.  

Right now Firefox and Safari percent-encode non-ASCII characters in the fragment.  Chrome percent-encodes non-ASCII characters in the fragment if the scheme is not a special scheme.  Edge does not percent-encode any non-ASCII characters in the fragment.

This change is needed to continue to support percent-encoding non-ascii characters after a '#' in a data URL, which works in Safari, Chrome, and Firefox.

-- 
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/url/issues/150