URL#origin is `"null"` when using file protocol which is different with browser

[JounQin]

Version

v24.14.0

Platform

arwin JounQin---MacBook-Pro-Max.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19 19:30:44 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6000 arm64

Subsystem

No response

What steps will reproduce the bug?

new URL('file:///home/user/document.html#section')
URL {
  href: 'file:///home/user/document.html#section',
  origin: 'null',
  protocol: 'file:',
  username: '',
  password: '',
  host: '',
  hostname: '',
  port: '',
  pathname: '/home/user/document.html',
  search: '',
  searchParams: URLSearchParams {},
  hash: '#section'
}

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior? Why is that the expected behavior?

Origin should be file://

What do you see instead?

"null"

Additional information

No response

[thisalihassan]

Not an issue "null" is correct per the WHATWG URL Standard

4.7. Origin

Unfortunate as it is, this is left as an exercise to the reader. When in doubt, return a new opaque origin.

[JounQin]

Not an issue "null" is correct per the WHATWG URL Standard

🤦‍♂️ Thanks for your clarification, so it seems the browsers are not following WHATWG spec.

[thisalihassan]

they all are WHATWG spec doesn't say "you must return opaque origin for file:" it says "this is left as an exercise to the reader."
Firefox returns "null" as origin while chrome doesn't

[JounQin]

❤️

It's still strange that Node.js follows FireFox instead of Chrome considering v8.