Skip to content

Path segments can be empty - #919

Merged
annevk merged 1 commit into
mainfrom
annevk/path-and-file-url-validity
Jul 1, 2026
Merged

annevk merged 1 commit into
mainfrom
annevk/path-and-file-url-validity

Conversation

@annevk

@annevk annevk commented Jun 30, 2026 •

Copy link
Copy Markdown
Member

E.g., https://example.com///this///is///fine.

And file:// can be followed by nothing in theory.

Helps with #704.


Preview | Diff

E.g., https://example.com///this///is///fine.

And file:// can be followed by nothing in theory.

Helps with #704.
@annevk
annevk requested a review from domenic June 30, 2026 12:55
@annevk annevk added the topic: validation Pertaining to the rules for URL writing and validity (as opposed to parsing) label Jun 30, 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>
@annevk
annevk merged commit 1505976 into main Jul 1, 2026
2 checks passed
@annevk
annevk deleted the annevk/path-and-file-url-validity branch July 1, 2026 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: validation Pertaining to the rules for URL writing and validity (as opposed to parsing)

Development

Successfully merging this pull request may close these issues.

2 participants