You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may reflect a few Xwayland issues. So it would be good to fix this specifically, but it also seems like a nice small test case for some Xwayland things that may impact other applications.
Not sure why the setOpacity(0); doesn't work. I would have though XWayland just turns that into a transparent Wayland surface without the compositor needing to do anything.
This shouldn't show in things like cosmic-workspaces. Either the workspaces protocol needs to pass through these flags, or with an X window ID, clients could fetch that and other things (like the window icon) from the X server themselves. The former is probably better, though it does mean more protocol bloat.
Or the compositor could have some heuristic to decide which X windows should just be omitted from the top-level info protocol altogether, which would probably make sense at least in this case.
Presumably things like i3 and sway have some heuristic that recognizes that a window like this should not be tiled, even though it's technically visible and has a size. Maybe that's related to setFlag(Qt::Dialog);.
The text was updated successfully, but these errors were encountered:
https://invent.kde.org/system/xwaylandvideobridge autostarts through
/etc/xdg/autostart
. But on Cosmic-comp, instead of being hidden it shows up as a normal window, all white.This may reflect a few Xwayland issues. So it would be good to fix this specifically, but it also seems like a nice small test case for some Xwayland things that may impact other applications.
https://invent.kde.org/system/xwaylandvideobridge/-/blob/master/src/contentswindow.cpp
Not sure why the
setOpacity(0);
doesn't work. I would have though XWayland just turns that into a transparent Wayland surface without the compositor needing to do anything.KX11Extras::setState(winId(), NET::SkipTaskbar | NET::SkipPager | NET::SkipSwitcher);
This shouldn't show in things like cosmic-workspaces. Either the workspaces protocol needs to pass through these flags, or with an X window ID, clients could fetch that and other things (like the window icon) from the X server themselves. The former is probably better, though it does mean more protocol bloat.
Or the compositor could have some heuristic to decide which X windows should just be omitted from the top-level info protocol altogether, which would probably make sense at least in this case.
Presumably things like i3 and sway have some heuristic that recognizes that a window like this should not be tiled, even though it's technically visible and has a size. Maybe that's related to
setFlag(Qt::Dialog);
.The text was updated successfully, but these errors were encountered: