Bug 443006 - Context menu header/title text is weirdly truncated
Summary: Context menu header/title text is weirdly truncated
Status: RESOLVED DUPLICATE of bug 450333
Alias: None
Product: Breeze
Classification: Plasma
Component: QStyle (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-27 11:49 UTC by Carl Schwan
Modified: 2022-02-16 15:15 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
menu (24.07 KB, image/png)
2021-09-27 11:49 UTC, Carl Schwan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Schwan 2021-09-27 11:49:43 UTC 
Created attachment 141946 [details]
menu

SUMMARY


STEPS TO REPRODUCE
1. Open Kmail composer with the global menu enabled
2. click on the hamburger menu
3 .

OBSERVED RESULT
See screenshot

EXPECTED RESULT
Text is truncated correctly and not just cut 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE tumbleweed (but using kdesrc-build)
KDE Plasma Version: master
KDE Frameworks Version: master
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Felix Ernst 2021-09-28 14:11:39 UTC 
This bug happens in any QMenu that adds a section (QMenu::addSection(text)) with text that is very very long.

The bug is encountered in KHamburgerMenu when a global menu bar is used because in that case no "Show Menubar" action is visible which reduces the overall width of this menu so it is narrower than the "<amount> Menu Bar Exclusive Actions" section text.

I think the correct fix for this isn't in KConfigWidgets since this is a general problem on how section text sometimes doesn't fit in the QMenu. Maybe it should be fixed in the style.

>EXPECTED RESULT
>Text is truncated correctly and not just cut
Alternatively the width of the QMenu should be wider so everything fits.
Comment 2 Nate Graham 2021-10-17 22:22:39 UTC 
*** Bug 443805 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2022-02-16 15:15:30 UTC 
Just fixed in Bug 450333!

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