Bug 403749 - Drag-n-drop moves a maximized borderless origin position instead of restoring it when using a 1.5 display scale
Summary: Drag-n-drop moves a maximized borderless origin position instead of restoring...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: 5.14.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-29 23:48 UTC by Viorel-Cătălin Răpițeanu
Modified: 2021-12-07 04:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
mgraesslin: X11+


Attachments
kwinrc file (999 bytes, text/plain)
2019-01-30 20:06 UTC, Viorel-Cătălin Răpițeanu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Viorel-Cătălin Răpițeanu 2019-01-29 23:48:30 UTC
SUMMARY
Draging a maximized window when a 1.5 scale is applied will result in it moving it's origin point (instead of restoring it to an unmaximized state).

STEPS TO REPRODUCE
1. Add 'BorderlessMaximizedWindows=true' to your kwinrc
2. Add a 1.5 scale for your output
3. Open an application that supports dragging from within itself (like KDevelop)
4. Maximize it. (the border should be hidden now)
5. Click inside your application and drag and drop it else where.

OBSERVED RESULT
The application remains in a maximized state (with it's border hidden) while it's changing it's origin point.

EXPECTED RESULT
The application should return to a window mode (unmaximized), before changing it's origin point.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3

ADDITIONAL INFORMATION
This was tested using kwin for X11.
Comment 1 Viorel-Cătălin Răpițeanu 2019-01-29 23:49:00 UTC
Video of the issue:
https://drive.google.com/open?id=1lFxOT4Oyom4ksBYcVEawEvC8MxzpjhJt
Comment 2 Vlad Zahorodnii 2019-01-30 17:00:48 UTC
Hmmm, can't reproduce. Could you please post your kwinrc and breezerc?

> 2. Add a 1.5 scale for your output
So... This happens only with 1.5 scaling factor, right?
Comment 3 Viorel-Cătălin Răpițeanu 2019-01-30 20:03:42 UTC
(In reply to Vlad Zagorodniy from comment #2)
> Hmmm, can't reproduce. Could you please post your kwinrc and breezerc?
> 
> > 2. Add a 1.5 scale for your output
> So... This happens only with 1.5 scaling factor, right?

This reproduce on 2 different computers with 1.5 scale. This doesn't happen when there isn't any scaling (scale 1).
Comment 4 Viorel-Cătălin Răpițeanu 2019-01-30 20:06:23 UTC
Created attachment 117744 [details]
kwinrc file

I don't have any breezerc file.
Comment 5 Vlad Zahorodnii 2019-02-07 00:56:57 UTC
Hmm, I still can't reproduce it. Also, I'm wondering how scaling could affect net move resize.
Comment 6 kde.org 2021-11-07 10:51:25 UTC
Can you please create new user with default settings from Plasma 5.23 and only make the configuration changes you describe below and let us know if the issue is still present. We need to be able to reliably reproduce the issue to have a shot at fixing it.
Comment 7 Bug Janitor Service 2021-11-22 04:38:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2021-12-07 04:36:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!