Bug 21972 - Windows drive letters are not handled correctly when resolving relative URLs.
Summary: Windows drive letters are not handled correctly when resolving relative URLs.
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-30 10:02 PDT by Brett Wilson (Google)
Modified: 2024-04-19 09:05 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brett Wilson (Google) 2008-10-30 10:02:20 PDT
The relative URL "/foo" when resolved on the base URL "file:///C:/bar" should give "file:///C:/foo" rather than "file:/foo". Note however that "/c:/foo" in this situation should still resolve to "file:///C:/foo".

The relative URL "../../../" when resolved against "file:///C:/foo" should give "file:///C:/" rather than "file:/".

Links on web pages of the form "c:\foo", "c:/foo", or "c|\foo" should be treated as absolute URLs to "file://C:/foo". This comes up when viewing local pages that have hardcoded paths.
Comment 1 Ahmad Saleem 2024-04-19 09:05:17 PDT
@Fuji - do we have such issue anymore since `win-cairo` is only Windows port as of right now.

I am inclined toward to mark this as 'RESOLVED CONFIGURATION CHANGED' or 'WONTFIX' since if we have this issue since 2008, we would have newer bug reports as well.