ozone/wayland: tabdrag: Skip unset_maximized during window drag
Differently from other platforms, under Wayland, unmaximizing the dragged window before starting the drag loop is not needed as it is assumed to be handled at compositor side, in extended-drag sessions [1][2]. Just like in xdg_toplevel_surface's move request. Thus, this CL patches WaylandToplevelWindow::Restore() function such that it is no-op if there is a window drag session running. Bug: 896640 Test: ozone_unittests --gtest_filter='*WaylandWindowDragControllerTest.RestoreDuringWindowDragSession*' [1] https://docs.google.com/document/d/1s6OwTi_WC-pS21WLGQYI39yw2m42ZlVolUXBclljXB4/edit#heading=h.gjdgxs [2] https://source.chromium.org/chromium/chromium/src/+/master:third_party/wayland-protocols/unstable/extended-drag/extended-drag-unstable-v1.xml Change-Id: Ifd07958604554686ca3bd7f7964b2dab80442316 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2508235 Commit-Queue: Nick Yamane <nickdiego@igalia.com> Auto-Submit: Nick Yamane <nickdiego@igalia.com> Reviewed-by:Maksim Sisov (GMT+2) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#823525}
Showing
Please register or sign in to comment