Repository navigation
Path segments can be empty - #919
Merged
Merged
Conversation
E.g., https://example.com///this///is///fine. And file:// can be followed by nothing in theory. Helps with #704.
domenic
approved these changes
Jul 1, 2026
domenic
added a commit
to jsdom/whatwg-url
that referenced
this pull request
Jul 1, 2026
Allow URL string validation to treat path-absolute strings as slash-separated URL path segments, including empty segments and bare file://. Remove prefix dispatch that assumed scheme-relative and path-absolute alternatives were disjoint. Follows whatwg/url#919. Co-authored-by: codex <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
E.g., https://example.com///this///is///fine.
And file:// can be followed by nothing in theory.
Helps with #704.
Preview | Diff