Bug 489506 - Default panel float-defloat behavior causes application window painted 2 times (visual glitch)
Summary: Default panel float-defloat behavior causes application window painted 2 time...
Status: RESOLVED DUPLICATE of bug 485145
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 6.1.1
Platform: Neon Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-30 17:00 UTC by kdetester
Modified: 2024-06-30 20:26 UTC (History)
2 users (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 kdetester 2024-06-30 17:00:13 UTC
SUMMARY
Default panel float-defloat behavior causes application window painted 2 times (visual glitch)

STEPS TO REPRODUCE
1. Make sure nothing is open in maximized mode and panel is floating.
2. Open and maximize (if not already maximized) KDE Settings or Dolphin or GIMP or any other application.

OBSERVED RESULT
The application is painted for panel floated scree size. Then panel de-floats (with smooth animation) and moves to the bottom of screen. Then the application re-paints with the new screen size. Especially, observe the bottom part of application to see this problem.

This visual glitch is clear visible in many applications and is annoying.

EXPECTED RESULT
The application window if launched in maximized mode, from launch of the application should it should (virtually) see thw whole region available assuming the panel is de-floated. And along with the application launch animation the panel also should smoothly de-float. Meaning, the maximized application should not see the screen size of floated panel to be painted as application window size.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Up to date Neon, Plasma 6.1.1
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Comment 1 cwo 2024-06-30 20:26:52 UTC
Thank you for the bug report! This issue has already been filed; please follow that bug report for updates on a fix.

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