Bug 500813 - Panel applets unexpectedly react to "Make Window Fullscreen" shortcut
Summary: Panel applets unexpectedly react to "Make Window Fullscreen" shortcut
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.3.2
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-27 14:28 UTC by Filip
Modified: 2025-03-01 09:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
showcase (2.20 MB, video/x-matroska)
2025-02-27 14:28 UTC, Filip
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Filip 2025-02-27 14:28:21 UTC
Created attachment 178943 [details]
showcase

SUMMARY
Panel applets react to "Make Window Fullscreen" shortcut.

I can see a reason for it to be intentional, but I would then rather use "Maximize Window" shortcut and fix the animation.

STEPS TO REPRODUCE
1. Open applet on panel
2. Trigger "Make Window Fullscreen" shortcut

OBSERVED RESULT
Applet is fullscreened (doesn't look like it because of size limit I guess, but you can't resize it in that state, only trigger the shortcut again)

EXPECTED RESULT
Nothing happens
Alternatively use "Maximize Window" shortcut instead if we want this behavior

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 1 Nate Graham 2025-02-28 22:19:14 UTC
Not intentional, however I can't reproduce this. Not with Kickoff and not with that exact shortcut set for the action, either.
Comment 2 TraceyC 2025-02-28 22:23:20 UTC
I was able to see what you describe using the clock widget on 6.3.2. I wasn't able to reproduce this on git-master
It looks like this has been fixed. You'll see the fix on your system either in 6.3.x or 6.4
Feel free to re-open this report if you can still reproduce the behavior after 6.3.2
Comment 3 Filip 2025-03-01 09:01:02 UTC
I checked it on master and I can't reproduce it there. Thanks.