Open Bug 1872790 Opened 9 months ago Updated 4 months ago

wayland wayfire no DE sizemodechange not received

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 121
defect

Tracking

()

People

(Reporter: je-vv, Unassigned)

References

(Blocks 2 open bugs)

Details

Steps to reproduce:

On pure wayland ("MOZ_ENABLE_WAYLAND=1" and "GDK_BACKEND=wayland"), using wayfire as compositor and no DE, start Firefox with one window, open the Browser Console (Ctrl+Shift+J) or via Tools > Browser Tools > Browser Console.

Paste this into the window and hit enter:

top.window.addEventListener("sizemodechange", () => console.log("sizemodechange received"))

Now minimise the main window leaving the console open. The log "sizemodechange received" should show up. But it doesn't.

This affects not just Firefox, but also Thunderbird (the steps can be followed there).

Not sure if related, but on Thunderbird is that maximizing misplaces Thunderbird, and it's quite hard to place Thunderbird where it should be after attempting to maximize it.

Actual results:

The log "sizemodechange received" doesn't show up. There might be side effects associated to not recognizing sizemodechange.

Expected results:

sizemodechange should have been recognized, and then the log should have printed "sizemodechange received"

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.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: wayland
Priority: -- → P3

(Martin asked for an update to this in bug 1542587 comment 11.)

As far as I can see, TB relies on the "sizemodechange" notification here:
https://searchfox.org/comm-central/rev/055bf5ef7eba067990f20681b25ca40238931414/mail/components/extensions/parent/ext-mail.js#1576
(I don't know what that code does.)

I assume that the JS from comment #0 top.window.addEventListener("sizemodechange", () => console.log("sizemodechange received")) can be executed in FF to see whether the event fires.

Blocks: 1627479
You need to log in before you can comment on or make changes to this bug.