https://bugs.kde.org/show_bug.cgi?id=448856

--- Comment #5 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
@Ethan not sure if you're the right person to speak or should I go downstream,
but SDL's initialization sequence of initially fullscreen windows is not
optimal with kwin.

with kwin_wayland, the ideal startup sequence looks as follows:

-> create xdg_toplevel
-> set app_id, min/max size
-> call set_maximized or set_fullscreen if the window has to be displayed
maximize or fullscreen, respectively
-> create xdg_toplevel_decoration if needed and set the preferred mode
-> wl_surface_commit()

<- kwin responds with a configure event
-> start painting \o/

In other words, kwin_wayland really wants to have as much as possible
initialization happen before the first surface commit. See also
https://bugs.chromium.org/p/chromium/issues/detail?id=1268308

But it seems like SDL can issue several set_fullscreen requests and commit the
surface multiple times with no buffer attached until the window is finally
mapped.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to