Skip to content

Close gap between URL writing and parser sections#905

Open
annevk wants to merge 4 commits into
mainfrom
annevk/writing-parser-gap
Open

Close gap between URL writing and parser sections#905
annevk wants to merge 4 commits into
mainfrom
annevk/writing-parser-gap

Conversation

@annevk

@annevk annevk commented Apr 14, 2026

Copy link
Copy Markdown
Member
  1. Domain-percent-encoded: validation error for percent-encoding in domains (e.g., exam%70le.com).
  2. Validation error when strict Unicode ToASCII would fail (e.g., _dmarc.example.com).
  3. Invalid-URL-unit: now also emitted for spaces in opaque paths (e.g., foo:bar baz).
  4. Writing grammar: non-special absolute URLs now allow opaque paths directly, fixing foo:a:b being incorrectly invalid.

Fixes #796. Fixes #797. Helps with #704.


Preview | Diff

1. Domain-percent-encoded: validation error for percent-encoding in domains (e.g., exam%70le.com).
2. Validation error when strict Unicode ToASCII would fail (e.g., _dmarc.example.com).
3. Invalid-URL-unit: now also emitted for spaces in opaque paths (e.g., foo:bar baz).
4. Writing grammar: non-special absolute URLs now allow opaque paths directly, fixing foo:a:b being incorrectly invalid.

Fixes #796. Fixes #797. Helps with #704.
@annevk annevk force-pushed the annevk/writing-parser-gap branch from 24aef76 to 535b834 Compare June 26, 2026 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

"valid domain" does not match validation errors in the host parser "valid host string" does not allow for percent-encoding

1 participant