SUMMARY Task manager Adaptive opacity shows transparent instead of opaque when VS Code is full screen. STEPS TO REPRODUCE 1. Install VS Code 2. Launch VS Code with the following command-line options: /opt/visual-studio-code/code --enable-features=UseOzonePlatform --ozone-platform=wayland --no-sandbox --unity-launch %F OBSERVED RESULT In maximised window mode of VS Code the Plasma task manager shows transparent instead of opaque. EXPECTED RESULT Task Manager should be opaque when the VS Code window is maximised. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
When you launch it like that, is it *actually* maximized, or does its window simply take up the whole screen space? They are different. In order to be counted as maximized, it needs to actually be in the maximized state by clicking the Maximize button on the toolbar. Can you verify? If so, this is probably Bug 437089.
Well i think it was when i maximised it, as i was minimising and maximising it to see if it would work. Some days before it didn't. Let me explain first that if launched with these parameters VS Code starts with native Wayland, but has this issue of having both the native KDE title bar and its own client title bar showing at the same time. This has been fixed by Google Chrome upstream and in Electron 14, but it will be a while until that goes into VS Code. With all that said, now it works if i maximise it, but with a delay of about 3 seconds. This messed up state of the titlebar might be a reason or might not...
> With all that said, now it works if i maximise it, but with a delay of about 3 seconds That strongly suggests to me that this is a bug in VSCode. Evidently it takes several seconds to communicate "I'm maximized!" to the window manager, which Plasma asks when it needs to determine if it should make your panels opaque or transparent. Can you file a bug report on VSCode for that? The fact that it doesn't *launch* in a maximized state with the args you gave it would probably be separate issue. Specifically Bug 437089.