-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
Remove nonstandard WHATWG URL url.toString(true) #10750
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Closed
domenic opened this issue
Jan 12, 2017
· 3 comments
· May be fixed by adamlaska/node#112, aliscco/alisco-node#665, leonardoadame/node#187, aliscco/alisco-node#691 or aliscco/alisco-node#698
Closed
Remove nonstandard WHATWG URL url.toString(true) #10750
domenic opened this issue
Jan 12, 2017
· 3 comments
· May be fixed by adamlaska/node#112, aliscco/alisco-node#665, leonardoadame/node#187, aliscco/alisco-node#691 or aliscco/alisco-node#698
Labels
whatwg-url
Issues and PRs related to the WHATWG URL implementation.
Comments
definitely agree that this is not ideal. I would like to have a way of getting back the unicode/idna encoding of the URL without punycode tho so moving something into the |
Just noticed #10857 is gonna fix this (although |
Fixed in c5e9654...0d9ea4f |
This was referenced Nov 28, 2023
This was referenced Nov 29, 2023
This was referenced Nov 29, 2023
This was referenced Nov 30, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
As with originFor and friends, it should ideally move to a separate export on the
url
module, instead of extending the standard object with unspecified behavior.The text was updated successfully, but these errors were encountered: