1644245 - Firefox menus showing up on different monitor from the one Firefox is on

Status: RESOLVED DUPLICATE of bug 1592416

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

Description

[David Elstner]

This has been reported in the past and marked as resolved. The bug is back!

This bug has reappeared in 77.0.1 (64-bit) on MacOS Catalina Version 10.15.5 running on a MacBook Pro (16-inch, 2019). When Firefox is on second screen (Apple Thunderbolt Display, 27-inch, 2560x1440), AMD Radeon Pro 5500M 8 GB graphics), menus appear on the built-in display. This second monitor is connected via a Thunderbolt 2 cable through an adapter to a USB-C on the MacBook Pro.

This issue doesn't occur when Firefox is on the MacBook Pro.

The issue does occur when Firefox is on the third monitor (HP 25bw Display, 25-inch (1920x1080) connected via HDMI cable through an adapter to a USB-C.

This problem only started about a week or two ago but I can't confirm which version of Firefox that I had before, however, I do have automatic updates turned on so that's probably easy to figure out what the previous version was.

This is really annoying!

-Dave

Comment 1

[Stephen A Pohl [:spohl]]

Could you run mozregression[1] to see when this started happening? If you have never run mozregression before, simply run these three commands in a Terminal window:

sudo easy_install pip
sudo pip install -U mozregression --ignore-installed
mozregression --good 2017-01-01

You can adjust the last line to match a date when the issue did not reproduce for you.

A number of Firefox versions will open in succession to narrow down when this started occurring. Simply type "good" or "bad" in Terminal based on whether or not a build reproduces the bug. Once finished, please post the output from the last run. It should give a last good and first bad revision as well as a link to look at the changesets in that range. Thank you!

[1] https://mozilla.github.io/mozregression/

Comment 2

[David Elstner]

Attachment: Firefox Menu Problem.jpg

The regression tool did not find a problem but I've attached a photo showing that it exists!

Comment 3

[David Elstner]

I didn't see this after I saved my update!

% mozregression --good 2017-01-01 16:39:33

---

You should use a config file. Please use the --write-config command line flag to help you create one.

---

0:00.16 INFO: No 'bad' option specified, using 2020-06-10
0:02.54 INFO: Testing good and bad builds to ensure that they are really good and bad...
0:02.54 INFO: Downloading build from: https://archive.mozilla.org/pub/firefox/nightly/2017/01/2017-01-01-03-02-04-mozilla-central/firefox-53.0a1.en-US.mac.dmg
===== Downloaded 100% =====
0:03.61 INFO: Running mozilla-central build for 2017-01-01
0:29.47 INFO: Launching /private/var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmpxywztpzb/FirefoxNightly.app/Contents/MacOS/firefox
0:29.47 INFO: Application command: /private/var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmpxywztpzb/FirefoxNightly.app/Contents/MacOS/firefox -foreground -profile /var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmpniacr4na.mozrunner
0:29.52 INFO: application_buildid: 20170101030204
0:29.52 INFO: application_changeset: cb9f43eb552570e185e95dfc8acb9f9fbe47ae17
0:29.52 INFO: application_name: Firefox
0:29.52 INFO: application_repository: https://hg.mozilla.org/mozilla-central
0:29.52 INFO: application_version: 53.0a1
Was this nightly build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry' or 'exit' and press Enter): good
8:44.61 INFO: Using local file: /var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmp3mqvnjel/2020-06-10--mozilla-central--firefox-79.0a1.en-US.mac.dmg (downloaded in background)
8:44.61 INFO: Running mozilla-central build for 2020-06-10
9:01.73 INFO: Launching /private/var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmpnk42d41i/Firefox Nightly.app/Contents/MacOS/firefox
9:01.73 INFO: Application command: /private/var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmpnk42d41i/Firefox Nightly.app/Contents/MacOS/firefox -foreground -profile /var/folders/0m/dyhh4l1s3vn4ph0pzrwxh5tm0000gn/T/tmpbm94npvi.mozrunner
9:01.80 INFO: application_buildid: 20200610043607
9:01.80 INFO: application_changeset: b2df79a80c0303df9d710800ae37dce56847eef5
9:01.80 INFO: application_name: Firefox
9:01.80 INFO: application_repository: https://hg.mozilla.org/mozilla-central
9:01.80 INFO: application_version: 79.0a1
Was this nightly build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry' or 'exit' and press Enter): good
12:01.96 ERROR: Build was expected to be bad! The initial good/bad range seems incorrect.

Comment 4

[Stephen A Pohl [:spohl]]

Ah, so this may be related to your Firefox profile. Are you saying that you haven't seen this problem since running mozregression? Or does your original Firefox installation still exhibit this problem?

Comment 5

[David Elstner]

I'm still having the problem. The photo I attached was immediately after running the regression tool. The photo shows Firefox on the 2nd monitor with one of the bookmark menus selected and the menu showing up on the primary monitor (the MacBook Pro).

The problem exists if I have Firefox on monitor 3 with the same behavior, that is, menus showing up on monitor 1.

If Firefox is on monitor 1 then there is no problem.

Comment 6

[Stephen A Pohl [:spohl]]

Could you check if this reproduces with a new profile[1] and/or in safe mode[2]?

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Multiple_profiles
[2] https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Comment 7

[David Elstner]

Well, it's my fault and not a Firefox bug. I do want to report what caused the reported behavior so that the solution may be offered to others if it comes up again.

MacOS provides the capability for the user to set a preferred display (when there is more than one) for an application to appear on. After launching Firefox, if it is moved to a different display and a menu is opened the menu will still appear on the preferred display. That explains why menus were always appearing on display number one since I had set it as the preferred monitor.

To fix this, I set the "Options => Assign To" value to "None" in the jump menu for Firefox. I've attached an image showing the jump menu to help visualize what I've described.

Sorry for taking up your time.

Thanks,
-Dave

Comment 8

[David Elstner]

Attachment: Firefox jump menu on MacOS

This image is referenced in my last comment.

Comment 9

[Stephen A Pohl [:spohl]]

This was actually a legitimate issue and not your mistake. We should still show menus on the screen that Firefox is on, even if you have it assigned to a different display. Luckily, this has been addressed in bug 1592416 and should be fixed in Nightly. Thanks again for reporting the issue!