| Summary: | Regression: Suspend prompt of Lock/Logout widget does not display correctly (buttons are obscured) | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | delcypher |
| Component: | visuals | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | delcypher |
| Priority: | NOR | ||
| Version First Reported In: | 4.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot of incorrectly displayed suspend prompt
Screenshot of incorrectly displayed suspend prompt from widget on panel |
||
|
Description
delcypher
2013-02-10 09:04:26 UTC
Created attachment 77082 [details]
Screenshot of incorrectly displayed suspend prompt
This is a screenshot of the incorrectly displayed suspend prompt shown by clicking on a "Lock/Logout" widget on the desktop. It can be seen that the prompt is too small vertically and the buttons are clipped so that the text in the buttons is NOT VISIBLE!
From a usability standpoint that's pretty bad, It's impossible to tell which button is "OK" and which is "Cancel". From testing it appears that the left button is "OK" and the right button is "Cancel" but I shouldn't have to guess!
Created attachment 77083 [details]
Screenshot of incorrectly displayed suspend prompt from widget on panel
This is a screenshot of the incorrectly displayed suspend prompt shown by clicking on a "Lock/Logout" widget that is in a panel. It can be seen that the prompt is too small vertically and the buttons are clipped so that the text in the buttons is NOT VISIBLE!
From a usability standpoint that's pretty bad, It's impossible to tell which button is "OK" and which is "Cancel". From testing it appears that the left button is "OK" and the right button is "Cancel" but I shouldn't have to guess!
Hmm I seems that my bug is actually a duplicate of bug #313943 ( https://bugs.kde.org/show_bug.cgi?id=313943 ) although I think my description of the problem is slightly more accurate. *** This bug has been marked as a duplicate of bug 313943 *** |