Inconsistent behavior while parsing the port number

[igibek]

Hey, I noticed inconsistent behavior while the port number is parsed in the URL. Specifically, if the port number is equal to 80, whatwg-url will drop it from the returned value. See examples below:

Expected behavior:

new URL("http://admin:secret@google.com:1234/root?foo=bar&boo=baz#anything")
/* returns
{
  scheme: 'http:',
  user: 'admin',
  password: 'secret',
  host: 'google.com',
  port: '1234',
  path: '/root',
  query: '?foo=bar&boo=baz',
  fragment: '#anything'
}
*/

Inconsisted behavior:

new URL("http://admin:secret@google.com:80/root?foo=bar&boo=baz#anything")
/* returns
{
  scheme: 'http:',
  user: 'admin',
  password: 'secret',
  host: 'google.com',
  port: '',
  path: '/root',
  query: '?foo=bar&boo=baz',
  fragment: '#anything'
}
*/

[domenic]

Yep, that's what the spec says to do! https://url.spec.whatwg.org/#ref-for-concept-url-port%E2%91%A2

[igibek]

I missed that part. Thanks for the quick response. However, in general, I think it is non-intuitive behavior from spec :)