mirror of
https://github.com/brl/mutter.git
synced 2024-11-25 09:30:45 -05:00
4f68713020
This addresses the following race condition: 1. Window+MetaFrame are created non-fullscreen, _MUTTER_FRAME_EXTENTS is initialized through widget measuring, accounting for frame. 2. Window and MetaFrame become fullscreen. 3. MetaFrameContent gets first size allocation, already fullscreen. 4. Borders were initialized to 0,0,0,0, become set to 0,0,0,0 correctly reflecting fullscreen, however notify::borders is not emitted. 5. _MUTTER_FRAME_EXTENTS stays accounting for the frame extents. It sounds sensible to have the borders initialized to a meaningful value, so account for the first time the border would be set due to the content being (re)sized, and let this first value trigger notify::borders resulting in _MUTTER_FRAME_EXTENTS updates. Since all later _MUTTER_FRAME_EXTENTS changes happen through content resizes, we only have to cater for this initial handover between the frame/content initialization paths done through widget measuring and the later paths done through MetaFrameContent resizes. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2937 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3476> |
||
|---|---|---|
| .. | ||
| backends | ||
| common | ||
| compositor | ||
| core | ||
| frames | ||
| meta | ||
| tests | ||
| wayland | ||
| x11 | ||
| meson.build | ||
| meta-private-enum-types.c.in | ||
| meta-private-enum-types.h.in | ||