Hi All,
After looking into it a bit more, it appears as if the proper thing to do
is to allow a null surface in wl_pointer.leave, wl_keyboard.leave, etc.
Right now, that's what the clients are seeing anyway because
wl_surface_destroy destroys the associated proxy so there is no valid way
to call a
Hi All,
This week, some of the wl_resource pointer changes that I made to weston
caused a bug related to destroyed resources in keyboard/pointer focus
handling. This bug brings up an interesting protocol issue in how we
should handle pointer focus with respect to resource destruction.
The specifi