Bug 445854 - Kickoff launcher pane responds like a regular window when using Windows key + arrow key shortcuts
Summary: Kickoff launcher pane responds like a regular window when using Windows key +...
Status: RESOLVED DUPLICATE of bug 411462
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: 5.23.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-21 09:04 UTC by mjeff
Modified: 2021-11-21 23:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mjeff 2021-11-21 09:04:51 UTC
SUMMARY
I use the Win+<arrow key> shortcuts to snap windows to different sides of the screen and different heights/widths.

I happened to have the Kickoff launcher in focus when I performed that shortcut thinking I was in a different window.

What ended up happening was the Kickoff menu itself began to respond like a typical window and behaved in a similar manner to a regular window (the shortcut allowed me to expand the Kickoff menu to full screen height, full screen width, etc.)

The main issue with this is that I can't find a way to resize it back to the size it was initially since its default size is smaller than what the keyboard shortcuts allow. The expected behavior is that it shouldn't resize in that manner based on keyboard shortcuts

STEPS TO REPRODUCE
1. Open the Kickoff launcher
2. With the launcher open and in focus, press win+up arrow key (this can actually be any arrow key)
3. Observe the launcher size changing

OBSERVED RESULT
Launcher changes size

EXPECTED RESULT
Nothing happens as the launcher shouldn't be able to be resized in that manner (at least not without a simple way of changing it back to its default size)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE
KDE Plasma Version: 5.23.3
KDE Frameworks Version:  5.88.0
Qt Version: 5.15.2
Comment 1 Patrick Silva 2021-11-21 23:09:50 UTC

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