ozone/wayland: Do not allow to attach buffers until surface's configured
This CL fixes spurious problems when new frames are sent and a buffer is attached earlier than WaylandSurface/WaylandPopup are configured. Thus, add a new interface into the WaylandWindowObserver that notifies the WaylandBufferManagerHost if the window has been configured. The manager resets |configured_| variable upon ResetWindowContents as long as the wl_surface becomes unmapped and it is reinitialized with new xdg_surface, xdg_toplevel or whatever only during the next Show() call. In that case, it will be configured again and the host will be notified about that. Bug: 1083949 Change-Id: I9895bc8876748ba69bc0461c2aeb300175a40065 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207172Reviewed-by:Nick Yamane <nickdiego@igalia.com> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#770567}
Showing
Please register or sign in to comment