Bug 406017 - Key events sent to applications when moving window with keyboard
Summary: Key events sent to applications when moving window with keyboard
Status: RESOLVED DUPLICATE of bug 368827
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.15.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-29 20:27 UTC by Samuel Gilbert
Modified: 2019-04-16 23:20 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Gilbert 2019-03-29 20:27:50 UTC
SUMMARY

Key events are sent to applications when moving windows with the keyboard.  This behaviour is clearly unintended.  For example when moving a window of a text editor, the cursor is moved in the text when pressing the arrow keys.

STEPS TO REPRODUCE
1. Open any application the arrow keys and ENTER are handled by the application. (For example: Kate with some text or code)
2. ALT-F3 -> ALT-M -> ENTER
3. Use the arrow keys move the window

OBSERVED RESULT
The window moves, but the application also reacts to the key events

EXPECTED RESULT
The window moves and nothing is changed in the application (it does not receive key events until the move is completed by hitting ENTER or clicking with the mouse)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.13.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
I also noticed that the behaviour is not exactly the same when trying to move non-KDE applications such as Firefox: The arrow keys do not move the window and ENTER does not complete the move operation.  The only way to complete the move operation is to left-click with the mouse.  The key events are handled by the application as if no move operation had been started.
Comment 1 Patrick Silva 2019-04-16 23:20:52 UTC

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