Bug 370001 - Subpixel AA turned off on some UI controls
Summary: Subpixel AA turned off on some UI controls
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.7.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-04 20:43 UTC by EP
Modified: 2021-03-10 00:16 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
red -- subpixel AA off, green -- on (59.11 KB, image/png)
2016-10-04 20:54 UTC, EP 		Details
case 2 (49.57 KB, image/png)
2016-10-04 20:55 UTC, EP 		Details
case 3: taskbar button and tooltip (21.59 KB, image/png)
2016-10-04 20:56 UTC, EP 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description EP 2016-10-04 20:43:11 UTC 
I remember there was a bug filed few years ago about inability of the qt engine to apply subpixel aa on transparent backgrounds (e.g. task manager buttons), but can't find it now -- may this is related to that.
Don't know if this is a kde bug or a qt bug, hope you will sort it out.

Reproducible: Always

Steps to Reproduce:
1. Have subpxel AA turned on
2. Open Plasma Desktop Settings for example
3. See how fonts are rendered on the UI controls (such as dropdown menus, buttons)

Actual Results:  
Subpixel AA is turned off on some of the controls

Expected Results:  
Subpixel AA is turned on everywhere
Comment 1 EP 2016-10-04 20:54:32 UTC 
Created attachment 101418 [details]
red -- subpixel AA off, green -- on
Comment 2 EP 2016-10-04 20:55:42 UTC 
Created attachment 101419 [details]
case 2
Comment 3 EP 2016-10-04 20:56:19 UTC 
Created attachment 101420 [details]
case 3: taskbar button and tooltip
Comment 4 Christoph Feck 2016-10-07 02:30:08 UTC 
This could be https://bugreports.qt.io/browse/QTBUG-22334 if some Plasma QML components render to an offscreen Pixmap.
Comment 5 Nate Graham 2021-03-10 00:16:30 UTC 
This was an issue with PlasmaComponents2 which uses QtQuickControls1, and it has been resolved as of a few years ago.