Bug 441870 - Extra border in context menu on HiDPI display (with fractional global scaling)
Summary: Extra border in context menu on HiDPI display (with fractional global scaling)
Status: RESOLVED DUPLICATE of bug 418166
Alias: None
Product: Breeze
Classification: Plasma
Component: QStyle (show other bugs)
Version: 5.22.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-01 15:36 UTC by Artem Kliminskyi
Modified: 2021-09-02 18:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot of the context menu (42.49 KB, image/png)
2021-09-01 15:36 UTC, Artem Kliminskyi 		Details
Screenshot with intersection (97.10 KB, image/png)
2021-09-01 15:45 UTC, Artem Kliminskyi 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Artem Kliminskyi 2021-09-01 15:36:44 UTC 
Created attachment 141221 [details]
Screenshot of the context menu

SUMMARY
In Dolphin, KMail, Gwenview, KolourPaint and other Qt apps (but not on the GTK apps and desktop) there is extra right and bottom border if the fractional global scaling enabled (125% for example).

STEPS TO REPRODUCE
1. Set the global scaling to 125%.
2. Open Qt application.
3. Right mouse click - and see that borders.

OBSERVED RESULT
Right and bottom border is greater than others.

EXPECTED RESULT
Symmetric context menu.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Screenshot in the attachments and sorry for my bad English.
Comment 1 Artem Kliminskyi 2021-09-01 15:45:09 UTC 
I just noticed that it is not just white border. 
Look the intersection with text and pictures in the "Screenshot with intersection" attachment.
Comment 2 Artem Kliminskyi 2021-09-01 15:45:35 UTC 
Created attachment 141222 [details]
Screenshot with intersection
Comment 3 Nate Graham 2021-09-02 18:45:33 UTC 

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