Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)

mertcanaltin left a comment (whatwg/url#874)

@domenic @annevk I've implemented this in jsdom/whatwg-url and
  updated the test expectations:

  **Implementation PR:** jsdom/whatwg-url#304

  **Test Results:**
  - ✅ **5353/5381 tests passing (99.5%)**
  - ✅ All basic Windows path scenarios working:
    - Drive letter paths: `C:\path\file.txt` →
  `file:///C:/path/file.txt`
    - UNC paths: `\\server\share\file.txt` →
  `file://server/share/file.txt`
    - Unicode characters correctly percent-encoded
    - Backslashes converted to forward slashes

  **27 Edge Cases Need Spec Clarification:**

  The failing tests fall into these categories:

  1. **Invalid drive letters** (should these fail or be accepted?)
     - `CC:\path\file.txt`
     - `C:\\\path\file.txt` (triple backslash)
     - `C:\\` (just drive + backslashes)

  2. **Device paths** (should these be supported?)
     - `\\.\Y:`
     - `\\.\y:`

  3. **Special characters in paths:**
     - `C:\folder#fragment\file.txt` (hash in path)
     - `C:\folder%20encoded\file.txt` (percent-encoding)
     - `C:\folder\file?.txt` (question mark)
     - Paths with tabs (`\t`)

  4. **UNC paths with base URL:**
     - `\\x\hello` against `http://example.org/foo/bar`

  Could you provide guidance on the expected behavior for these edge
  cases? I'm happy to update both the spec and tests once we clarify
  the intended behavior.

  **Note:** WPT tests have been updated to use percent-encoded
  Unicode (matching actual browser behavior).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/874#issuecomment-3369353488
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/pull/874/c3369353488@github.com>