1721494 - [Wayland]Menu list doesn't appear on first click

Status: RESOLVED DUPLICATE of bug 1721036

(Core :: Widget: Gtk, defect)

Description

[Kevin Locke]

With sway 1.6 and Firefox Nightly with MOZ_ENABLE_WAYLAND=1, when the button is clicked to open a menu, the menu list doesn't appear until the mouse is moved to where the list would be. This reliably occurs the first time the button is clicked. Subsequent clicks are intermittent. An example:

1. Run Firefox.
2. Open Manage Bookmarks (Ctrl+Shift+O).
3. Click "Import and Backup".

At this point the "Import and Backup" button is darkened to show activation, but the list of menu items ("Backup...", "Restore...", etc.) does not appear. If the mouse is moved down to where they should appear, they do.

Mozregression:

Last good revision: 5214a9d3bb7a3a7daa3bc4322130a2900fa6f8ec
First bad revision: fbd0995a14990b138449f1f00f7a3315ca2b3d8b
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5214a9d3bb7a3a7daa3bc4322130a2900fa6f8ec&tochange=fbd0995a14990b138449f1f00f7a3315ca2b3d8b

It appears this was regressed by Bug 1717451.

Thanks,
Kevin

Comment 1

[Robert Mader [:rmader]]

Hm, sounds similar to either bug 1721298 (in case you have gfx.webrender.compositor.force-enabled set) or, more likely, bug 1721036 - but then the regression window would not obviously make sense :/

Comment 2

[Kevin Locke]

Thanks :rmader! gfx.webrender.compositor.force-enabled is false in the default prefs, but "Compositing: WebRender" is shown in about:support under Graphics, if that's relevant.

The issue sounds similar to Bug 1721298, although for me the issue always occurs on the first click and intermittently on subsequent clicks, where that one sounds like it occurs reliably on all clicks except the first. :/

I can also confirm that I'm affected by Bug 1721036. Not sure if they're related. Perhaps it's not as reliable on the first click as I thought in older versions? It seems reliable in the current version, but I'll double-check the mozregression range to confirm. Let me know if there's anything else I can do to help narrow it down.

Comment 3

[Robert Mader [:rmader]]

Thanks. To me this sounds strongly like bug 1721036. Thinking about bug 1717451 it wouldn't be surprising if it made the bug appear more often. In order to verify, you can try disabling widget.wayland.multi-buffer-software-backend.enabled - if that fixes the issue it's definitely bug 1721036 (working on that right now).

Comment 4

[Kevin Locke]

Good call! I'm not able to reproduce the issue with widget.wayland.multi-buffer-software-backend.enabled:false. Closing as a duplicate of Bug 1721036. Thanks :rmader!