Skip to content
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.

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

Clarify URL string spec reference #2318

Merged
merged 2 commits into from
Feb 7, 2017
Merged

Clarify URL string spec reference #2318

merged 2 commits into from
Feb 7, 2017

Conversation

tstarling
Copy link
Contributor

The URL standard says "A URL is a universal identifier. To disambiguate from a URL string it can also be referred to as a URL record." So it's not correct to refer to this definition of "URL" for the validity requirements of an href attribute, which contains a string, not a record. I assume it was intended to refer to a "URL string", which is (more or less) the valid input to the URL parser.

The URL standard says "A URL is a universal identifier. To disambiguate
from a URL string it can also be referred to as a URL record." So it's
not correct to refer to this definition of "URL" for the validity
requirements of an href attribute, which contains a string, not a record.
I assume it was intended to refer to a "URL string", which is (more or
less) the valid input to the URL parser.
@domenic
Copy link
Member

domenic commented Feb 3, 2017

This is a great fix, although we may want to wait on whatwg/url#228 in case we end up changing "URL string" to "valid URL string" or similar.

@annevk annevk merged commit ba265b7 into whatwg:master Feb 7, 2017
@annevk
Copy link
Member

annevk commented Feb 7, 2017

I'm not sure how long that's going to take since the changes requested in that PR are rather elaborate. So I've gone ahead and merged this.

@annevk
Copy link
Member

annevk commented Feb 7, 2017

Thanks @tstarling!

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.

3 participants