Parsing of "http://../" is not correct #82
Closed
Conversation
This file contains 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
rmisev
changed the title
|
@domenic Seems like this is not a recent spec change but has been here for a while so should be a patch release I think. |
domenic
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Apr 24, 2017
The test covers https://url.spec.whatwg.org/#concept-ipv4-parser 6.1 item: > 1. If part is the empty string, return input. Related issue: jsdom/whatwg-url#82
This was referenced Dec 7, 2022
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.
http://../is parsed tohttp://0.0.0.0/But must be parsed to
http://../It looks like IPv4 parser treats empty parts as 0, but https://url.spec.whatwg.org/#concept-ipv4-parser 6.1 says: