Bug 447160

Summary: Chromium based browsers when launched under wayland doesn't have close animations
Product: [Plasma] kwin Reporter: Samuel Reddy <samuelsumukhreddy>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal Keywords: usability, wayland-only
Priority: NOR    
Version First Reported In: 5.23.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Samuel Reddy 2021-12-18 10:39:52 UTC 
SUMMARY:
When you launch Chromium based browsers under wayland by running with the --ozone-platform=wayland command line flag and then close the browser, there is no close animation. So if you have a fade close animation, there is no fading on the close animation on Chromium Wayland.


STEPS TO REPRODUCE:
1. Open a Chromium based browser on Wayland using the --ozone-platform=wayland command line flag
2. Close the browser
3. No close animation when you have one in enabled in desktop effects settings

OBSERVED RESULT:
There is no close animation

EXPECTED RESULT:
There should be a close animation

SOFTWARE/OS VERSIONS:
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx
Memory: 5.7 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Comment 1 Vlad Zahorodnii 2022-01-11 09:28:43 UTC 
Can't reproduce with beta (98) and dev chrome. It appears like google chrome doesn't update surface properties after the compositor asks it to terminate anymore.
Comment 2 Samuel Reddy 2022-03-09 06:27:37 UTC 
Can reproduce on Chromium 99.0.4844.51.