Bug 34138 - [Qt] .ICO format images are not loaded on Anomaly Browser
Summary: [Qt] .ICO format images are not loaded on Anomaly Browser
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P3 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2010-01-25 10:44 PST by jtkbugz
Modified: 2010-03-17 08:11 PDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jtkbugz 2010-01-25 10:44:54 PST 
.ICO format images are not loaded on Bedrock Browser
Comment 1 Tor Arne Vestbø 2010-03-05 08:01:56 PST 
Please follow the QtWebKit bug reporting guidelines when reporting bugs.

See http://trac.webkit.org/wiki/QtWebKitBugs

Specifically:

  - The 'QtWebKit' component should be used for bugs/features in the QtWebKit API layer, not to signify that the bug is specific to the Qt port of WebKit

    http://trac.webkit.org/wiki/QtWebKitBugs#Component

  - Priority is set by developers when scheduling and triaging tasks, please leave this at the default priority.

    http://trac.webkit.org/wiki/QtWebKitBugs#Priority

  - Choose a descriptive summary/title for the bug and prefix the summary with "[Qt]" if the bug only applies to the Qt-port.

    https://trac.webkit.org/wiki/QtWebKitBugs#Summary
Comment 2 Robert Hogan 2010-03-16 12:55:43 PDT 
Report is a bit cryptic and in absence of test case assume it's stating that the Bedrock browser does not display favicons. Closing as INVALID in absence of test case as per https://trac.webkit.org/wiki/QtWebKitBugs#Triagingbugs
Comment 3 Simon Hausmann 2010-03-17 08:11:29 PDT 
In addition there isn't really any ico image format specific code in WebKit that we use. It's just another image format that is handled through Qt's ico image format plugin. If that's built and available, then ico as well as the favicon feature work just fine. The plugin is built by default, so it may be a deployment problem.