-
-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make URL encoding fully WHATWG-compliant #1454
Conversation
Hey, much appreciated! Is there any chance you could add a test that would actually ensure compliance? |
Ugh, I'm confused. How do you write a test for something like this? This is quite literally the verbatim implementation of the spec:
What I mean to say is, isn't this something we just double, triple check manually here once and be done? P.s. I did notice the erroneous |
Woah I must have been drunk or something to make such basic errors. Almost looks like I couldn't read. |
Fair enough. By the way, do you think it might be nice to try to upstream this into |
Thanks for this. I cross-checked the spec and this seems good! |
Yeah I questioned why this wasn't already a part of |
That's really odd. Thanks for looking into it. Perhaps open an issue to discuss upstream? Seems like it was removed a few years ago and the mindset might've changed. |
Found this: servo/rust-url#837. Seems like someone has the same idea but the PR looks to be stalled. |
While debugging the failing tests in #1093, I ran into some trouble with improperly-encoded URLs at the front end. It turns out percent-encode sets defined by miniserve aren't fully compliant with the spec. This PR fixes that.