Bug 453447 - Dragging the titlebar of a new window that starts maximized doesn't move the titlebar relative to its original position
Summary: Dragging the titlebar of a new window that starts maximized doesn't move the ...
Status: RESOLVED DUPLICATE of bug 449105
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-06 02:24 UTC by Noah Davis
Modified: 2022-05-06 15:20 UTC (History)
1 user (show)

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

Attachments
New maximized window top left corner goes to mouse position (3.47 MB, video/x-matroska)
2022-05-06 02:28 UTC, Noah Davis 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Noah Davis 2022-05-06 02:24:03 UTC 
SUMMARY
I've attached a video of the problem.
This only happens for windows that start maximized.

STEPS TO REPRODUCE
1. Open Firefox
2. Maximize Firefox
3. Open a new Firefox window. It should be maximized by default if the existing Firefox window is maximized.
4. Drag the titlebar until the window starts moving

OBSERVED RESULT
The window's top left corner will be on the mouse cursor's position.

EXPECTED RESULT
The titlebar should move relative to its original position like it normally does.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220503
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 30.8 GiB of RAM
Graphics Processor: AMD RENOIR
Manufacturer: Eluktronics
Product Name: THINN-15
Comment 1 Noah Davis 2022-05-06 02:28:11 UTC 
Created attachment 148595 [details]
New maximized window top left corner goes to mouse position
Comment 2 Nate Graham 2022-05-06 15:20:48 UTC 

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