Closed Bug 1818805 Opened 2 years ago Closed 2 years ago

New Private Window keyboard shortcut on Firefox for Mac does not work. It worked in the previous version.

Categories

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

Firefox 109
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jrdn_dsouza, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

Press SHIFT + COMMAND + P on the keyboard.

Actual results:

Nothing happened.

Expected results:

A New Private Window should have opened up.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Cocoa
Product: Firefox → Core

I'm unable to reproduce this. Could you run mozregression 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 python3 -m pip install -U mozregression --ignore-installed
mozregression --good 2017-01-01

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!

Severity: -- → S3
Flags: needinfo?(jrdn_dsouza)
Priority: -- → P3

Hy, thank you for the bug report!
Unfortunately I could not reproduce your issue. Would you be so kind as to answer a few questions so we can investigate this further?

Thank you.

Hi there!

I ran the commands and they worked well. The Firefox instances displayed no issues on my end.

For some strange reason, my main Firefox issue seems to have disappeared. It was present for a few days before I submitted the bug report. After which, I tried it again and it worked as expected. I myself have not been able to replicate the issue. Since the problem seems to be resolved on my end (and since I'm unable to replicate the origin of the issue), if someone can close this thread, that would be great. Thank you!(In reply to Stephen A Pohl [:spohl] from comment #2)

I'm unable to reproduce this. Could you run mozregression 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 python3 -m pip install -U mozregression --ignore-installed
mozregression --good 2017-01-01

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!

Flags: needinfo?(jrdn_dsouza)

Thanks for letting us know.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME

(In reply to Ardelean Oana from comment #3)

Hy, thank you for the bug report!
Unfortunately I could not reproduce your issue. Would you be so kind as to answer a few questions so we can investigate this further?

Thank you.

Hi there! Thanks for taking the time to look into this. You can read my response below, however, I believe the issue is now resolved. If it does happen again, I will play around with it a bit before submitting another response. Thank you again!

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