Bug 148598
| Summary: | [Win] File-based URL's cause the ParsedURLStringTag constructor to ASSERT | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brent Fulgham <bfulgham> |
| Component: | WebCore Misc. | Assignee: | Brent Fulgham <bfulgham> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | bfulgham |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=148596 | ||
Brent Fulgham
If you create a URL from a Windows file path (e.g., "C:/Some/Test/URL.html"), the Cache logic will eventually call the URL constructor that takes a ParsedURLStringTag argument. This constructor asserts that the URL created by the string matches the internal string representation.
This turns out to be false on Windows, because the URL parsing logic skips the colon in the "C:/Some/Test" and changes it to "C/Some/Test", which does not match.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brent Fulgham
It looks like this happens in DumpRenderTree, but not MiniBrowser.
Brent Fulgham
This issue has nothing to do with the URL implementation. It's a bug in a platform library.