1468029 - new private window shortcut not working

Status: RESOLVED WORKSFORME

(Firefox :: Keyboard Navigation, defect)

Description

[hotknive]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180605171542

Steps to reproduce:

ctrl+shift+p not working in latest version of Mozilla Firefox (60.0.2) 64 bit Windows 10,
although if I click the new private window on the menu it worked. but still the shortcut not working, I have tried reinstalled the firefox still no luck


Actual results:

ctrl+shift+p doing nothing instead of opening new private window


Expected results:

new private window should be opened

Comment 1

[Dão Gottwald [:dao]]

Can you still reproduce this bug? (I can't.)

Comment 2

[hotknive]

Sorry just replying on this bug, I have tried everything, reinstalling the firefox, updating to latest version(62.0.2 (64-bit)), all seem doing nothing for my case, please help. ctrl+shift+p still not working until now. 
And just ask information that you need, thank you

Comment 3

[Dão Gottwald [:dao]]

(In reply to hotknive from comment #2)
> Sorry just replying on this bug, I have tried everything, reinstalling the
> firefox, updating to latest version(62.0.2 (64-bit)), all seem doing nothing
> for my case, please help. ctrl+shift+p still not working until now. 
> And just ask information that you need, thank you

Can you try to find a regression range using mozregression? See https://mozilla.github.io/mozregression/

Comment 4

[hotknive]

Okay I will try mozregression, I will report back as soon I find the regression range. Thanks

Comment 5

[Marco Castelluccio [:marco]]

(Even if we don't know the regression range yet, this is still a regression)

Comment 6

[Dão Gottwald [:dao]]

(In reply to Marco Castelluccio [:marco] from comment #5)
> (Even if we don't know the regression range yet, this is still a regression)

How would you know? Can you reproduce the bug? If so, can you help find the regression range?

The reporter hasn't said that this worked in some previous version, so as the triage owner I'm not gonna treat this as a regression until we know more.

Comment 7

[Marco Castelluccio [:marco]]

(In reply to Dão Gottwald [::dao] from comment #6)
> (In reply to Marco Castelluccio [:marco] from comment #5)
> > (Even if we don't know the regression range yet, this is still a regression)
> 
> How would you know? Can you reproduce the bug? If so, can you help find the
> regression range?
> 
> The reporter hasn't said that this worked in some previous version, so as
> the triage owner I'm not gonna treat this as a regression until we know more.

From his words, it seemed like a regression to me ("not working in latest version" and "I will report back as soon I find the regression range").
Let's wait for his confirmation then.