-
Notifications
You must be signed in to change notification settings - Fork 139
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
EOF after stand-alone drive-letter. #304
Comments
It's an issue of current specification. It looks like the cause is a logic error in the file state of basic URL parser. The base's path is copied, because
I will try to fix it. |
rmisev
added a commit
to rmisev/url
that referenced
this issue
Apr 30, 2017
annevk
pushed a commit
that referenced
this issue
May 3, 2017
triple-underscore
added a commit
to triple-underscore/triple-underscore.github.io
that referenced
this issue
May 3, 2017
…e6b251 Fixes whatwg/url#304 和訳には織り込み済み(原文を論理的な対偶に変換している + [ ε の利用]による結果、修正不要)
rmisev
added a commit
to upa-url/upa
that referenced
this issue
May 24, 2020
rmisev
added a commit
to upa-url/upa
that referenced
this issue
May 24, 2020
URL statndard issue: whatwg/url#304 Follows whatwg/url#305
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reference implementation currently parses
C|
againstfile://host/dir/file
asfile://host/dir/C|
.Against the same base URL,
C|
is parsed asfile://host/dir/C|
C|#
is parsed asfile:///C:#
C|?
is parsed asfile:///C:?
C|/
is parsed asfile:///C:/
/C|
is parsed asfile:///C:
I am not (yet) sure if this is according to the current specification or an issue with the reference implementation. I would propose changing this behaviour to have
C|
yieldfile:///C:
.The text was updated successfully, but these errors were encountered: