Bug 398984 - Breeze settings too narrow to display text of drop-down lists
Summary: Breeze settings too narrow to display text of drop-down lists
Status: RESOLVED DUPLICATE of bug 385096
Alias: None
Product: Breeze
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2018-09-23 10:51 UTC by Karl Ove Hufthammer
Modified: 2018-09-23 19:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing the Breeze configure window (179.65 KB, image/png)
2018-09-23 10:51 UTC, Karl Ove Hufthammer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Ove Hufthammer 2018-09-23 10:51:52 UTC
Created attachment 115180 [details]
Screenshot showing the Breeze configure window

SUMMARY
In the Breeze settings dialogue, the default window width is too narrow to display the contents of the two drop-down lists.


STEPS TO REPRODUCE
1. Navigate to ‘System Settings → Application Style → Widget Style → Breeze → Configure’.
2. Observe that the text in the two drop-down lists are cut off. (Might depend on your font size / DPI settings, so I’ll attach a screenshot.)
3. Observe that the text is even more cut-off if you click on one of the drop-down lists.

EXPECTED RESULT
The windows should be wide enough to display the entire content of the drop-down lists.


ACTUAL RESULT
The text in dro drop-down lists is cut off.


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
A proper fix should *automatically* increase the window width to ensure that the entire text is visible. Just making the default size a bit wider is a not a good solution, as that won’t necessarily work with translations (that may be longer than the English text) and non-default font sizes.
Comment 1 Patrick Silva 2018-09-23 19:27:12 UTC

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