https://bugs.kde.org/show_bug.cgi?id=477737
--- Comment #2 from Vlad Zahorodnii <vlad.zahorod...@kde.org> --- If blender initializes xdg-toplevels as follows -> wl_compositor.create_surface -> xdg_wm_base.get_xdg_surface -> xdg_surface.get_toplevel -> xdg_decoration_manager_v1.get_toplevel_decoration -> xdg_toplevel_decoration_v1.set_mode -> wl_surface.commit wait for the configure event -> wl_surface.attach(500x500) -> wl_surface.commit then the toplevel won't shrink. If the server side decoration is requested **after** the surface has been mapped, what happens next is up to the compositor. In case of kwin, it tries to maintain same frame geometry, so the space for window borders will be subtracted from the surface size. If blender indeed initializes like that, we recommend to request a server side decoration **before** the first wl_surface commit. It's going to fix this issue and it's going to ensure that there's no any flickering caused by server side decoration being missing for one frame. -- You are receiving this mail because: You are watching all bug changes.
