-
Notifications
You must be signed in to change notification settings - Fork 139
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
Ensure the API roundtrips for opaque paths #728
Conversation
As opaque paths can end in U+0020, those trailing U+0020 code points need to be removed from the path when both query and fragment become null. Tests: ... Fixes #651.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be missing something but I think to make web-platform-tests/wpt#37556 pass you need to modify the pathname setter as well. I'm getting data:space
vs. data:nospace
and sc:space
vs. sc:nospace
failures when I try to implement this in jsdom/whatwg-url.
Thanks, I first thought I indeed had to update the |
…ue paths, a=testonly Automatic update from web-platform-tests URL: hash/search roundtripping with opaque paths For whatwg/url#728. -- wpt-commits: c8ad978c6ff0792e5bb29da0eff600b4ba18cc46 wpt-pr: 37556
…ue paths, a=testonly Automatic update from web-platform-tests URL: hash/search roundtripping with opaque paths For whatwg/url#728. -- wpt-commits: c8ad978c6ff0792e5bb29da0eff600b4ba18cc46 wpt-pr: 37556
As opaque paths can end in U+0020, those trailing U+0020 code points need to be removed from the path when both query and fragment become null.
Fixes #651.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff