Bug 489076

Summary: NeoChat font rendering/smoothing is weird
Product: [Applications] NeoChat Reporter: Daniel Lo Nigro <sites+kdebugs>
Component: GeneralAssignee: Tobias Fella <fella>
Status: RESOLVED DUPLICATE    
Severity: normal CC: carl, postix, uriesk
Priority: NOR    
Version: 24.05.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Skinny 'l'
chonky "f"
one "r" is thicker than another

Description Daniel Lo Nigro 2024-06-23 23:18:30 UTC
Created attachment 170885 [details]
Skinny 'l'

SUMMARY
There's something not quite right with the font rendering in NeoChat. Some letters are too skinny, and some have bad kerning. Resizing the window a little bit helps sometimes. I have my screen set to 150% scaling, which may be contributing to it.

I don't think I've seen this in any other KDE apps. The settings page in NeoChat is fine and does not have the same issue.

It's hard to describe, so I'll attach a few examples.

STEPS TO REPRODUCE
1. Set screen to 150% scaling
2. Load NeoChat
3. Sign in
4. Enter a room and read text in it. Try resize the window a bit.

OBSERVED RESULT
Text rendering is weird

EXPECTED RESULT
Text rendering is not weird

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Comment 1 Daniel Lo Nigro 2024-06-23 23:18:49 UTC
Created attachment 170886 [details]
chonky "f"
Comment 2 Daniel Lo Nigro 2024-06-23 23:19:26 UTC
Created attachment 170887 [details]
one "r" is thicker than another
Comment 3 Andreas G 2024-07-09 09:27:23 UTC
This is a bug in qtwebengine:
https://bugreports.qt.io/browse/QTBUG-113574

You can work around it by setting the environment variable:
QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor
https://userbase.kde.org/Session_Environment_Variables

Or you just wait for qt 6.8 to get released and deployed. It will be fixed in the next version.
Comment 4 postix 2024-07-20 12:40:04 UTC
I assume this is a duplicate of 479891 otherwise please reopen again or mark as resolved upstream. :)

*** This bug has been marked as a duplicate of bug 479891 ***