Bug 486433

Summary: Wallpaper preview grid's header becomes displaced with certain ways of resizing the window
Product: [Plasma] plasmashell Reporter: rosswzyang
Component: Image & Slideshow wallpaper pluginsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: carlon.luca, hein, nate, notmart, qydwhotmail
Priority: NOR    
Version First Reported In: 6.0.4   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 6.1
Sentry Crash Report:
Attachments: reproduce step

Description rosswzyang 2024-05-02 08:48:47 UTC
Created attachment 169092 [details]
reproduce step

***
maxmize the wallpaper setting window then restore then maximize, you will find that the "top bar" has the wrong postion.
***
maxmize the wallpaper setting window then restore then maximize, you will find that the "top bar" has the wrong postion.

SUMMARY


STEPS TO REPRODUCE
1. maxmize the wallpaper setting window
2. restore wallpaper setting window
3. maximize the wallpaper setting window

OBSERVED RESULT
the "top bar" has the wrong postion.

EXPECTED RESULT
the "top bar" has the correct postion.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics
Memory: 27.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 83AS
System Version: XiaoXinPro 16 ARP8

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-05-03 20:11:40 UTC
Fixed by me with https://invent.kde.org/plasma/plasma-workspace/-/commit/49b45cb150c28f42e9e34b0041c6f764f2fdd313 for Plasma 6.1.

Then again I'm also the one who introduced the bug by creating that header component and forcing the grid view to use it when it didn't really want to, so don't give me too much credit for fixing it.
Comment 2 Nate Graham 2024-05-05 02:30:21 UTC
*** Bug 486550 has been marked as a duplicate of this bug. ***