arrow-down arrow at-sign bug check checkbox-checked checkbox-unchecked svg-checkmark chevron-right chevrons-right circle-down circle-left circle-right circle-up cloud2 svg-cross2 download download external-link filter github hash home leaf leaf left link-2 log-in log-out mail menu message-square minus plus radio-checked radio-checked2 radio-unchecked search settings spinner8 target twitter up upload-2 user users warning x zap
  • Home
  • Report a bug
  • Contribute
  • All issues
  • Login

URL: whatwg/url#873

Browser / Version: Chrome 138.0.0
Operating System: Mac OS X 10.15.7
Tested Another Browser: Yes Other

Problem type: Something else
Description: I've discovered an interesting behavior in the WHATWG URL specification: Windows file paths such as C:\path\file.node are considered valid URLs.
Steps to Reproduce:
The WHATWG URL spec is adding Windows file path handling.
Windows drive letter patterns ([a-zA-Z]:) should
automatically convert to file:/// URLs.

Expected behavior:
Input: C:\folder\file.txt
Output: file:///C:/folder/file.txt

Related links:

  • Spec PR: whatwg/url#874
  • Original issue: whatwg/url#873
  • Chromium bug: https://issues.chromium.org/issues/437449112
Browser Configuration
  • None

From webcompat.com with ❤️

Please login to edit issues.

View issue on Github

Shortcut: Press l on your keyboard to open the label editor. Shortcut: Press g on your keyboard to be taken to the GitHub view of this page.
Needs Triage
#170937

github.com - I've discovered an interesting behavior in the WHATWG URL specification: W

Opened: 2025-08-09
Reporter: mertcanaltin
Comments: 0
  • Home
  • List of issues
  • About
  • Contribute
  • Contact
  • Privacy Policy
  • Terms of Service
  • Code of Conduct