1558301 - Overflow Menu Disappears When Menu Item is Clicked On

Status: RESOLVED DUPLICATE of bug 1696786

(WebExtensions :: Frontend, defect, P3)

Description

[McCovican]

Attachment: Showing the menu disappearing after child buttons being clicked on

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

After updating to 68.0b8, opening the overflow menu and then clicking the button of an extension that you've placed into the overflow menu.

Actual results:

Upon clicking on one of the extension buttons that you've placed into the overflow menu, the overflow menu will simply disappear. The steps taken and result are the same as in 1445787 (however, this is on win7x64).

This seems to only affect extensions, and does not occur with any internal Firefox function buttons. Extensions that open their options in a new tab (rather than showing in the overflow menu itself) are also unaffected.

The overflow menu button will still show as being pressed (background colour of the button changes) after it disappears. In order to reopen the overflow menu, you'll have to click elsewhere first to make Firefox realise that the menu is now closed.

Expected results:

Should've resulted in the menu displaying the content of the extension you clicked on.

Comment 1

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

The priority flag is not set for this bug.
:ddurst, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Alex Cornestean]

Hello,

I am unable to reproduce the issue on the latest Release (67.0.4 / 20190619235627), Beta (68.0b14 / 20190627143605) or Nightly (69.0a1 / 20190701095406) under Windows 10 Pro 64-bit, Windows 7 64-bit, Windows 7 32-bit or macOS High Sierra 10.13.6.

I have checked with several add-ons you have shown in the attached video and also tried to reproduce the issue on Beta 68.0b8 on all above mentioned OS’s, with no success.

Are there any particular settings you might have enabled or other installed add-ons which might cause this erroneous behavior? Furthermore, have you tried reproducing the issue on a fresh install with a newly created profile?

Comment 3

[McCovican]

Hi,

While a new install isn't an option, a new profile was, and the issue did not occur on the fresh profile. I do know from testing before opening this bug that it still occurs even with most addons disabled (I obviously couldn't test it with all addons disabled, so I used a single addon to test and rotated through a few different ones). I realise that if I'd had half a braincell, I'd have started with trying a new profile.

It would indeed appear then that I, or an addon, has simply bodged a variable somewhere.

Unfortunately nothing specifically comes to mind in terms of settings - I don't think I've hand-modified too much in this install, but I've been a touch liberal with addons. I also tried resetting browser.uiCustomization.state entirely, but the issue persists, even now that I'm on b14.

I could provide a text list of the "important modified preferences" from about:support, or a screenshot of all modified variables from about:config, but I realise that this is now probably in the realm of a support query rather than a bug report, and would understand if you'd rather close this off now.

Many thanks.

Comment 4

[Alex Cornestean]

Hello,
I am still unable to reproduce so I can't provide a regression window on this.

Comment 5

[Alice0775 White]

McCovican,

Can you please paste a results of Help –> Troubleshooting Information( about:support )?

Comment 6

[McCovican]

Text copy: https://x.brutix.uk/1558301-text.txt
Raw data copy: https://x.brutix.uk/1558301-raw.txt

Comment 7

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

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 8

[Miruna Curtean]

Hello Alice,
Will there be any follow up on this issue based on the 'txt' files attached in comment?
Wondering if I should try reproducing by installing all the add-ons and setting the preferences according to the troubleshooting info or if that has already been done with no success.

Comment 9

[Alice0775 White]

Setting apz.popups.enabled = true triggers this issue.

I don't know why reporter changed this preferences.

Comment 10

[Miruna Curtean]

Thank you! I managed to reproduce this on Windows FF68 and further when the 'apz.popups.enabled' is set as true.
McCovican, could you please verify on the profile you had encountered the issue that setting it to default (false) solves it?

Comment 11

[McCovican]

Afraid I can't confirm it on the original issue profile - I admittedly got fed up and started largely from scratch. However, I can confirm that setting that to 'true' on my current profile (with pretty much the same extension list and all other system variables the same) does indeed invoke this issue for me - and setting it back to 'false' still properly clears the issue again.

Well hunted, and thank you for your time!

Comment 12

[Miruna Curtean]

For now I am marking this as NEW because if the apz.popups.enabled will be set by default to 'true' through 1493208 this will become a consistent issue.
Checked on Windows 10 Pro 64-bit, MAcOS Catalina 10.15 and 18.04.3 LTS on the latest Release version 74.0b7 (20200221211950, Beta 74.0b8 (20200224200110) and 75.0a1 (20200226092757) with the pref enabled and the behavior can be replicated.

With the exception of the latest Nightly version in Ubuntu I could reproduce using the following steps:

1. Launch FF browser and type in the about:config address.
2. Search for the apz.popups.enabled preference and set it to the 'true' value.
3. Restart browser an then from install and extension (ex:https://addons.mozilla.org/en-US/firefox/addon/styl-us/?src=search)
4. From hamburger menu Select Customize and drag the extension icon into the Overflow menu. Close Customize page.
5. Open overflow menu and select extension to open its popup menu.

Actual result:
Extension pup up menu is quickly open and closed and the user cannot interact with it.

Expected results:
The extension popup menu should remain open unless the user deliberately closes it through returning to overflow menu or clicking somewhere else on the screen.

Comment 13

[Miruna Curtean]

Hello,
I believe the Regression and Regression window tags no longer apply. I've taken a quick look on builds as far as 2017 and the behavior from comment 12 still occurs when the apz.popups.enabled preference is enabled.
Could you please remove them?

Comment 14

[Botond Ballo [:botond]]

I suspect this may be a duplicate of bug 1696786 as well.

McCovican, would you be able to test the behaviour in the latest Firefox Nightly and confirm the issue is resolved?

Comment 15

[Botond Ballo [:botond]]

I'm going to tentatively close this as a duplicate of bug 1696786. Please feel free to reopen if you're still experiencing this.