Firefox windows tiled to a screen-half on GNOME Wayland consistently land at the wrong on-screen position
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: giacecco, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:153.0) Gecko/20100101 Firefox/153.0
Steps to reproduce:
On GNOME Shell 50.1 / Mutter 50.1 (Ubuntu 26.04), Wayland session, tiled a Firefox window to a screen half — either by dragging it to a screen edge, or via a tiling keybinding. Tiling is handled by the Tiling Assistant GNOME Shell extension (tiling-assistant@ubuntu.com), which moves/resizes windows via Meta.Window.move_resize_frame(); GNOME's own native edge-tiling is disabled. Firefox: snap package, latest/stable, version 153.0-1 (revision 8664), running native Wayland (not XWayland — confirmed via xlsclients). Reproduced identically at native 5120x2880 @ integer scale 2.0, and at 3840x2160 @ fractional scale 1.5.
Actual results:
The window's size always ends up correct (confirmed pixel-perfect by screenshot measurement), but its position is wrong — it lands with an offset, often far enough that only a narrow, seemingly random-width sliver remains visible on-screen (the rest extends past the screen edge). The visible width varies non-deterministically between attempts against the same target: e.g. on a 5120px screen (LG Ultrafine 5k) expecting a 2560px left-half, measured right edges of 1440, 1369, 706, 1518, 430 (x3), 240, 523px; on a 3840px screen expecting 1920px: 420, 383, ~398, 523px.
Critical evidence that size and position are independently wrong: manually dragging the mis-tiled window by its titlebar (an ordinary move, no resize) snaps it immediately into a pixel-perfect half — proving the size was correct the whole time and only the automated tile action's positioning is wrong. Re-issuing the same automated tile command again (no manual drag in between) does not fix the position, and can land it further off.
Only Firefox is affected — a native-Wayland terminal, GNOME Files/Nautilus, and VS Code (XWayland) all tile correctly, same machine/session/mechanism. Suspected cause: Firefox acks/commits Wayland xdg_toplevel configure events asynchronously from its own thread, sometimes against a stale/intermediate size, so mutter's queued position ends up paired with the wrong committed geometry — a timing race. Possibly related: bug 1946184 (wrong sizing on Wayland after moving to tiled state, fixed Feb 2025), bug 1550721, bug 1589868. Ruled out as unrelated: widget.wayland.fractional-scale.enabled (tried both values), GTK_CSD=0, Tiling Assistant's tile-animation setting, and the monitor scale factor itself (1.5 vs 2.0 — identical either way).
Expected results:
The window should land flush against the tiled edge at the correct position, matching its (already-correct) size — i.e. occupy exactly the target half with no offset.
Comment 1•3 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Description
•