https://bugzilla.gnome.org/show_bug.cgi?id=780820
Jonas Ådahl <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #11 from Jonas Ådahl <[email protected]> ---
Hmm. I think the issue is that we add the Wayland client window to the stack
too early. The issue seems to be that we
1. Create a new window that cant be shown
2. Adds this new window on top of the stack
3. Closes the currently focused window
4. Finds a good candidate for new focused window
5. Raises that window
6. Show the window created in 1.
If step 6. would happen before 3. we're fine, but not when after.
I see two possible solutions to this:
1) Delay adding the window to the stack until it is "ready" (i.e. has a buffer
attached)
Not sure what funny side effects this may have; does anything assume a window
is always in the stack?
2) Delay creation of the MetaWindow until it's ready (i.e. has a buffer
attached)
Having a content-less MetaWindow has bitten us in the ass plenty of times, so
maybe we should stop having that. It'd require that we duplicate the relevant
state in meta-wayland-xdg-shell.c. meta-wayland-wl-shell.c already does this as
it needs to create/destroy the MetaWindow like crazy because wl_shell is crazy.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
