Bug 172975

Summary: Better look for konqueror taskbar icon
Product: [Applications] konqueror Reporter: fabio <povvy>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: faure, kdebugs
Priority: NOR    
Version First Reported In: 4.1.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screenshot
Composite image showing how bad it looks

Description fabio 2008-10-16 18:55:13 UTC 
Version:            (using KDE 4.1.2)
Installed from:    Ubuntu Packages

Depending on the size of the task manager applet in plasma, the icon representing konqueror looks in different ways, showing just the favicon in the case the taskbar is "small" enough, or both the favicon and the ugly default icon assigned to konqueror (screenshot attached); i'd like to be able to choose the way this works, without be forced to set the size of the taskbar; anyway, please set a better default icon for konqueror :)
Comment 1 fabio 2008-10-16 18:57:05 UTC 
Created attachment 27954 [details]
screenshot
Comment 2 David Faure 2008-10-16 19:08:44 UTC 
Actually, I was wondering if we should really show the favicon as the konq icon at all...
See http://kde.markmail.org/message/d6cegow7rwkkselr

What do you think?
Comment 3 fabio 2008-10-16 19:31:57 UTC 
I think the default setting used right now is not that bad, except for the konqueror icon that REALLY looks ugly; anyway i think u have to leave the choice to the user with a configuration dialog...
Comment 4 Stephan Sokolow 2009-02-10 22:23:16 UTC 
Created attachment 31205 [details]
Composite image showing how bad it looks

Whatever you decide, you'll want to at least feed the tooltip a larger version of the composite image you're using for the taskbar icon.

Using a 16x16px icon in a popup designed for something much bigger looks really ugly. The attached composite image should provide a good comparison.
Comment 5 Raphael Rosch 2020-02-27 00:29:43 UTC 
I propose this bug be closed. This appears to me to have been resolved