RESOLVED INVALID 50416
On windows drive letters are ignored for inline images by webkitgtk
https://bugs.webkit.org/show_bug.cgi?id=50416
Summary On windows drive letters are ignored for inline images by webkitgtk
jendrikseipp
Reported 2010-12-02 15:50:45 PST
This bug is probably windows specific. If there's an image at C:\image.jpg, and it is contained inside an HTML file, it is correctly displayed. However images that don't reside on C:\ cannot be displayed. The following table gives an overview: | Image path | HTML code | Observation | | C:\image.jpg | <img src="file://C:\image.jpg" border="0" alt=""/> | Works | | C:\image.jpg | <img src="file://D:\image.jpg" border="0" alt=""/> | Works although path is incorrect, drive letter can even be omitted | | D:\image.jpg | <img src="file://D:\image.jpg" border="0" alt=""/> | Image not found | | D:\image.jpg | <img src="file://C:\image.jpg" border="0" alt=""/> | Image not found (this is expected) | The issue is also discussed at https://bugs.launchpad.net/rednotebook/+bug/663944 .
Attachments
Alexey Proskuryakov
Comment 1 2010-12-02 22:34:38 PST
See also bug 21972 (duplicate?)
Martin Robinson
Comment 2 2010-12-03 08:38:46 PST
What version of WebKitGTK+ did you observe this with? This sounds like a libsoup bug.
jendrikseipp
Comment 3 2010-12-03 08:46:04 PST
Well, I used the dlls from http://opensourcepack.blogspot.com/2009/12/pywebkitgtk-windows-binary.html I think that was webkit version 1.2.0 and libsoup-2.4-1.dll (2.30).
jendrikseipp
Comment 4 2010-12-05 08:06:25 PST
I tried loading a problematic HTML file with midori and it works fine. I then copied the libsoup-2.4-1.dll file into my webkit directory, but it does not fix the error. So this may be something else than libsoup.
jendrikseipp
Comment 5 2010-12-05 14:09:08 PST
I think the problem was a missing slash. Apparently on windows you have to write file:///C:\myfile.txt instead of file://C:\myfile.txt
Martin Robinson
Comment 6 2010-12-05 15:41:06 PST
Okay. I'll close this bug then. Feel free to open a new bug if you encounter more issues.
Note You need to log in before you can comment on or make changes to this bug.