| Summary: | Making URL stop treating an assigned empty port as "0" instead of "" | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Maciej Stachowiak <mjs> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | annevk, ap, syoichi, webkit |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 128023 | ||
|
Description
Maciej Stachowiak
2014-01-30 15:04:59 PST
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. From our text expectation files: PASS URL: Setting <http://example.net:8080>.port = '' Port number is removed if empty is the new value |