-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
URL: setting port to the empty string should null port #4101
Conversation
Reviewers for this pull request are: @Sebmaster, @domenic, @frewsxcv, @mikewest, @rubys, @sideshowbarker, @smola, @tomalec, @xiaojunwu, and @zcorpan. |
FirefoxTesting revision 2e75d38 |
ChromeTesting revision 2e75d38 |
Setting it to the empty string should set the underlying port concept to null. See web-platform-tests/wpt#4101 for test changes and whatwg/url#113 for the change to the URL Standard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is for whatwg/url#113. LGTM
When it's setter is set to the empty string, it should set the underlying URL's port to null. Previously that was a no-op. This matches Firefox. (Chromium sets the port to zero.) Test: web-platform-tests/wpt#4101 Demo: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4054
Setting it to the empty string should set the underlying port concept to null. See web-platform-tests/wpt#4101 for test changes and whatwg/url#113 for the change to the URL Standard.
Setting it to the empty string should set the underlying port concept to null. See web-platform-tests/wpt#4101 for test changes and whatwg/url#113 for the change to the URL Standard.
No description provided.