Bug 510946 - Widgets' retract animation don't follow the auto-hide panel's retract animation
Summary: Widgets' retract animation don't follow the auto-hide panel's retract animation
Status: RESOLVED DUPLICATE of bug 470102
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (other bugs)
Version First Reported In: 6.4.5
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-23 07:59 UTC by Fernando M. Muniz
Modified: 2025-10-23 15:58 UTC (History)
2 users (show)

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


Attachments
Issue on Plasma 6.4.5 (1.12 MB, video/x-matroska)
2025-10-23 07:59 UTC, Fernando M. Muniz
Details
A collage of both gaps. (152.65 KB, image/jpeg)
2025-10-23 08:03 UTC, Fernando M. Muniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando M. Muniz 2025-10-23 07:59:10 UTC
Created attachment 186033 [details]
Issue on Plasma 6.4.5

STEPS TO REPRODUCE
Open the Application Launcher or the Calendar, then click on the desktop area.

OBSERVED RESULT
Their retraction doesn't follow the retraction of the auto-hide panel, making their fancy retract animation look disjointed.

EXPECTED RESULT
The widgets and application launcher should follow the auto-hide panel, to make their retract animation look natural.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.4-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 9 GB of RAM (8.1 GB usable)
Graphics Processor 1: Intel® Iris® Xe Graphics
Graphics Processor 2: NVIDIA GeForce GTX 1650
Manufacturer: LENOVO
Product Name: 82MG
System Version: IdeaPad Gaming 3 15IHU6
Comment 1 Fernando M. Muniz 2025-10-23 08:03:33 UTC
Created attachment 186034 [details]
A collage of both gaps.
Comment 2 Nate Graham 2025-10-23 15:58:12 UTC

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