Skip to content

Issues: whatwg/url

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.

Sign up for GitHub

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

61 Open 375 Closed
61 Open 375 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Formal IPv6 address definition clarification Standard could be clearer topic: model For issues with the abstract-but-normative bits
#839 opened Nov 26, 2024 by annevk
Update to Unicode 16.0.0 i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. topic: idna topic: parser
#836 opened Sep 21, 2024 by rmisev
3
Proposal: URL.setSearchParams() addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: api
#828 opened May 23, 2024 by jeremy-code
3
Punycode behavior for labels exceeding DNS length is ill-defined topic: idna topic: parser
#824 opened Mar 1, 2024 by hsivonen
8
Clearly mark conformance checking-only aspects of the IDNA section editorial Changes that do not affect how the standard is understood topic: idna topic: validation Pertaining to the rules for URL writing and validity (as opposed to parsing)
#816 opened Feb 2, 2024 by hsivonen
1
Web compatibility issue with various unknown (external) protocols like ed2k
#815 opened Jan 29, 2024 by evilpie
14
URL path comparison topic: model For issues with the abstract-but-normative bits
#814 opened Jan 26, 2024 by annevk
API mechanism for reporting validity errors addition/proposal New features or enhancements
#811 opened Jan 14, 2024 by jasnell
4
Use in HTTP2/3 Pseudo-Headers needs tests Moving the issue forward requires someone to write tests
#809 opened Dec 21, 2023 by ethanresnick
5
A '@' character in the host part of file URLs topic: file Aren't file: URLs the best? topic: parser
#805 opened Dec 5, 2023 by hayatoito
19
"valid domain" does not match validation errors in the host parser topic: validation Pertaining to the rules for URL writing and validity (as opposed to parsing)
#797 opened Oct 4, 2023 by annevk
1
"valid host string" does not allow for percent-encoding topic: validation Pertaining to the rules for URL writing and validity (as opposed to parsing)
#796 opened Oct 4, 2023 by annevk
URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true topic: parser
#784 opened Sep 5, 2023 by karwa
2
15
Enforce UTF-8 when url is given to the basic URL parser
#783 opened Sep 3, 2023 by annevk
1
Add URL.from(object) constructor? addition/proposal New features or enhancements needs concrete proposal Moving the issue forward requires someone to figure out a detailed plan needs implementer interest Moving the issue forward requires implementers to express interest topic: api
#782 opened Aug 28, 2023 by tabatkins
10
Differentiate from zero-sized fragment and no fragment in url addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: api
#779 opened Jul 13, 2023 by lu-zero
7
invalid-reverse-solidus error definition has character mixed up.
#772 opened May 26, 2023 by JamesNJep
4
Skipping an item while iterating is undefined clarification Standard could be clearer
#768 opened May 3, 2023 by SuperSonicHub1
1
Consider defining a primitive for a host-and-port parser
#767 opened Apr 2, 2023 by annevk
URLSearchParams append/set: variadic values argument? addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: api
#762 opened Mar 14, 2023 by bathos
6
Allow [ and ] as URL code-points topic: validation Pertaining to the rules for URL writing and validity (as opposed to parsing)
#753 opened Feb 11, 2023 by karwa
4
Allow specifying additional "special" schemes. clarification Standard could be clearer
#749 opened Feb 5, 2023 by tmccombs
3
Be clearer that non-UTF-8 code paths are only relevant for a small subset of implementations clarification Standard could be clearer
#746 opened Jan 24, 2023 by annevk
Meta: UTS46 feedback i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. meta Changes to the ecosystem around the standard, not its contents topic: idna
#744 opened Jan 23, 2023 by annevk
8
Allow encoding of null values in application/x-www-form-urlencoded.
#732 opened Jan 4, 2023 by ioquatix
17
ProTip! Follow long discussions with comments:>50.