Bug 127958 – Making URL stop treating an assigned empty port as "0" instead of ""

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: DOM

[Maciej Stachowiak]

Making URL stop treating an assigned empty port as "0" instead of "". Other browsers don't do it and it's probably wrong.

[akirk]

The spec (https://url.spec.whatwg.org/#dom-url-port) actually says this:

> If the given value is the empty string, then set context object’s url’s port to null.
And in the getter:

> If context object’s url’s port is null, return the empty string.
So in my opinion this needs to be changed to what the other browsers implemented.

[Anne van Kesteren]

From our text expectation files:

PASS URL: Setting <http://example.net:8080>.port = '' Port number is removed if empty is the new value