| Summary: | Task manager Adaptive opacity shows transparent instead of opaque when VS Code is maximised. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Lyubomir <liubomirwm> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Eike Hein <hein> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Lyubomir
2022-01-05 22:25:47 UTC
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. |