[Webkit-unassigned] [Bug 62459] New: Local files cannot load icons.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jun 10 07:53:42 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=62459
Summary: Local files cannot load icons.
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit API
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: rafael.lobo at openbossa.org
CC: darin at apple.com, sam at webkit.org, kling at webkit.org,
luiz at webkit.org, cmarcelo at webkit.org,
ademar.reis at openbossa.org
Created an attachment (id=96745)
--> (https://bugs.webkit.org/attachment.cgi?id=96745&action=review)
You cannot see this page's icon if you load it locally.
WebKit currently defines that only pages whose protocol is in HTTP family (HTTP or HTTPS) can have icons. So if you're designing a page like the one I've attached and want to preview it offline, you won't see any icon displayed. If you upload it to somewhere else, like dropbox, you'll be able to see it correctly.
This behavior looks unintuitive for me, so I would like to discuss why local files can't load icons too, as it can load anything else. Before looking into the code, I've searched examples with working icons because my first thought was that I could be using the icon keyword in the wrong way. I was puzzled because I couldn't reproduce it with my local file, but every page I've visited had an icon displayed. I didn't see anything explaining this on HTML5 specs. The closest thing I've found there was this:
"In the absence of a link with the icon keyword, for Documents obtained over HTTP or HTTPS, user agents may instead attempt to fetch and use an icon with the absolute URL obtained by resolving the URL "/favicon.ico" against the document's address, as if the page had declared that icon using the icon keyword."
Please share your thoughts about it. :)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list