Bug 21972
| Summary: | Windows drive letters are not handled correctly when resolving relative URLs. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brett Wilson (Google) <brettw> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, don.olmstead, fujii.hironori, jendrikseipp |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
Brett Wilson (Google)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
@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.