Created attachment 167801 [details] An image showing that the KAlarm Create New Alarm window get clipped SUMMARY My screen is 1920x1080 (1080p). When I set display scaling to 150% on Wayland, the New/Edit Display/Command/Email/Audio Alarm window getting clipped, making it impossible to click any buttons in the bottom row. STEPS TO REPRODUCE 1. Set display scaling to 150% 2. Open KAlarm 3. Create a new alarm or edit an existing alarm OBSERVED RESULT The create new alarm and edit alarm window getting clipped. EXPECTED RESULT The create new alarm and edit alarm window doesn't get clipped SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION KDE Neon 6.0 Graphics Platform: Wayland
When I use Wayland on Neon, I can drag the edit alarm window when holding the left mouse button down. This is the same behaviour as for the konsole "Edit Current Profile" window which is also too big for the display.
I can drag the window but the issue is that no matter what I do there's no way to drag the window so that I can click the buttons in the bottom row, like if I grab the title bar and drag it to the top it just maximize the window and the window is still being clipped
I don't mean drag the title bar. On my Neon, I can position the cursor anywhere in the middle of the window and drag it so that the buttons become visible.
Created attachment 167875 [details] An image showing that on X, Kalarm window is not clipped Oh I didn't know you can do that, always thought I have to drag the title bar to move the windows around However, I still think it would be better if I don't have to do so, like on X, where the window just fit and doesn't get clipped
Hmm I don't know what I did but now I can no longer drag the Create New Alarm / Edit Alarm window, it just refuse to go up when it reached the top, I have to use the Meta+Mouse drag trick to bypass it
Because Wayland is still a work in progress in some respects, and because KAlarm's behaviour is no different from Konsole's, it's entirely possible that this problem will resolve itself in some future Plasma version. If at some point the konsole window starts behaving properly but KAlarm's doesn't, please reopen this bug report. Or perhaps this bug should be raised against Plasma?