Bug 253008 - Important icon cut off
Summary: Important icon cut off
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-02 12:11 UTC by Matthias Fuchs
Modified: 2017-01-07 22:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
1 (16.39 KB, image/png)
2010-10-02 12:11 UTC, Matthias Fuchs
Details
2 (16.06 KB, image/png)
2010-10-02 12:11 UTC, Matthias Fuchs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Fuchs 2010-10-02 12:11:32 UTC
Created attachment 52158 [details]
1

Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

Best is to look at the screenshots, as two pictures say may than 2000 words. ;)

Reproducible: Always

Steps to Reproduce:
1. Check that the first item of the akregator list is not set to important
2. Set any item -- not the first -- to important, the icon is cut off (screenshot 1)
3. Set the first item to important --> all items are higher now and no icon is cut of (screenshot 2)
Comment 1 Matthias Fuchs 2010-10-02 12:11:56 UTC
Created attachment 52159 [details]
2
Comment 2 Christoph Feck 2010-10-02 13:28:58 UTC
It really depends on the font size. The small font you are using is smaller (14 pixels) than the icon size (16 pixels). Scaling the icon would make it blurry.
Comment 3 Matthias Fuchs 2010-10-02 17:45:02 UTC
That doesn't explain the issue I reported, namely that they are always cut off unless the first entry has an important icon.

Maybe either the height of the entries should not be fixed -- i.e. those with an icon are higher than those without (unless font size == icon size) -- or they should always have the height of the icon, no matter if displayed or not.
Comment 4 Denis Kurz 2016-09-24 19:42:00 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:27:26 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.