Mutter can reposition window on resize, if it is behind mutter's "bounding box". So, when you start winit window in maximized mode with CSD, mutter places its CSD behind the GNOME's status bar initially, and then sends configure with the exact same size as your current window. If winit decides to optimize calling frame.resize(..) in this case, we won't call set_geometry(we're calling it through resize) and GNOME won't reposition your window to be inside the "bounding box", which is not a desired behavior for the end user. |
||
|---|---|---|
| .. | ||
| event_loop.rs | ||
| keyboard.rs | ||
| mod.rs | ||
| pointer.rs | ||
| touch.rs | ||
| window.rs | ||