1761895 - [Wayland][Weston][Sway] Any click closes application menu or add bookmark panel

Status: RESOLVED INVALID

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

Description

[Kevin Locke]

With Firefox Nightly (Build 20220328213646) on Weston/Wayland, clicking in the Application Menu, Add Bookmark panel, more tools (toolbar overflow icons) panel, or presumably any other panel causes the panel to close rather than activating the clicked button/field. To reproduce:

1. Click the "Open Application Menu" (hamburger/3-bar) button.
2. Click "Help"

Rather than opening the Help menu, the application menu is closed.

Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1da49b17c30399c2c80886c322b7e6ac0469ef94&tochange=8a83aa3ec30981da1a9affddb67339f55959e529 suggesting this was regressed by Bug 1760276.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1760276

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

:stransky, since you are the author of the regressor, bug 1760276, could you take a look?
For more information, please visit auto_nag documentation.

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Please test on Mutter:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_different_Wayland_compositor
Can you please create a screencast of the issue?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Collect_information_for_a_bug_report
Thanks.

Comment 4

[Kevin Locke]

Attachment: Screencast of menu closing on click with Build 20220328213646 on Weston

(In reply to Martin Stránský [:stransky] (ni? me) from comment #3)

Please test on Mutter:

Sure. I'm unable to reproduce the issue on Mutter.

Can you please create a screencast of the issue?

Screencast attached. In the screencast, when I click on a menu item, the menu disappears.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1760276

Comment 6

[Kevin Locke]

Attachment: Screencast showing clicking on Location drop-down closes Add Bookmark panel on Sway 1.7 with FF build 20220406093646

I noticed a similar issue in Sway 1.7 regressed in the same pushlog: Clicking the Location drop-down in the Add Bookmark panel causes the panel to close. (Screencap attached.) As before, I'm unable to reproduce the issue in Mutter. Would you like me to open a separate bug for it, or adjust the summary of this one?

Comment 7

[Kevin Locke]

Attachment: Screencast on Sway showing the Add Bookmark popup being dismissed by the button tooltip

I noticed another interesting behavior tied to the same pushlog: In Sway 1.7 (but not Weston nor Mutter) the appearance of a tooltip dismisses the popup. I noticed it with the Awesome RSS addon, but was able to reproduce it with the Add Bookmark popup, as shown in the attached screencap. (Note: It requires mouse movement after clicking to cause the popup.)

Comment 8

[Kevin Locke]

Attachment: Screencast on Sway showing the Add Bookmark popup being dismissed by the button tooltip

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 10

[Pascal Chevrel:pascalc]

Could we get a severity set to this bug and potentially an assignee? Thanks

Comment 11

[Martin Stránský [:stransky] (ni? me)]

Should be already fixed for Mutter/KDE. If there's any remaining bug left for Sway it needs to be reported at Sway bug tracker as it's a bug in Sway Wayland compositor.

Comment 12

[Pascal Chevrel:pascalc]

Thanks, marking this as invalid then.

Comment 13

[Kevin Locke]

I have reproduced the issue in TinyWL and reported it as https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3449

(In reply to Pascal Chevrel:pascalc from comment #12)

Thanks, marking this as invalid then.

Interesting. If you don't mind me asking, what criteria are used to determine which issues are closed as invalid and which are assigned to Bug 1551279 and left open (which seems to be how most of my previous Sway-specific issues were handled)?

Comment 14

[Pascal Chevrel:pascalc]

(In reply to Kevin Locke from comment #13)

I have reproduced the issue in TinyWL and reported it as https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3449

(In reply to Pascal Chevrel:pascalc from comment #12)

Thanks, marking this as invalid then.

Interesting. If you don't mind me asking, what criteria are used to determine which issues are closed as invalid and which are assigned to Bug 1551279 and left open (which seems to be how most of my previous Sway-specific issues were handled)?

This is invalid because this is not a problem on the Firefox side but on the Sway side.

Comment 15

[Martin Stránský [:stransky] (ni? me)]

(In reply to Kevin Locke from comment #13)

I have reproduced the issue in TinyWL and reported it as https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3449

(In reply to Pascal Chevrel:pascalc from comment #12)

Thanks, marking this as invalid then.

Interesting. If you don't mind me asking, what criteria are used to determine which issues are closed as invalid and which are assigned to Bug 1551279 and left open (which seems to be how most of my previous Sway-specific issues were handled)?

The best solution may be to report that but at Sway bug tracker so we're sure it's not lost.
I keep the bugs open and track them in Bug 1551279 to make some record of issues and prevent duplicates.