为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

How to make macOS system keyboard shortcuts work?

  • 4 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 hongsy2006

more options

I set up an "App shortcut" hotkey in macOS's System Preferences binding ⌘⇧N (command+shift+N) to "New Private Window", but it doesn't work - when I press the key combination, a new *non-private* browser window opens instead.

In the first attached image, you can see the shortcut configured in the `Shortcuts` pane of macOS' System Preferences application.

In the second image, you can see Firefox's `File` menu open, and verify that the shortcut is correctly assigned to "New Private Window", where it has replaced the default ⌘⇧P.

However, as I said above, the custom key combination doesn't work - it seems to in fact trigger the regular "New Window", which is still the default ⌘N (command+N, no shift key).

Any one know if this is a known issue, and if there are any solutions?

Using a different key combination is not useful for me, since I'm trying to switch from Chrome and have ⌘⇧N very ingrained in my behavior (I pretty much always use private windows unless I need to log in to a site or explicitly want the history saved). If I can't have ⌘⇧N then I might as well just try to adjust to the default ⌘⇧P.

The fact that executing the shortcut brings up a non-private window makes the whole thing much worse - I'm ending up using non-private windows when I think I'm using private ones :/

I set up an "App shortcut" hotkey in macOS's System Preferences binding ⌘⇧N (command+shift+N) to "New Private Window", but it doesn't work - when I press the key combination, a new *non-private* browser window opens instead. In the first attached image, you can see the shortcut configured in the `Shortcuts` pane of macOS' System Preferences application. In the second image, you can see Firefox's `File` menu open, and verify that the shortcut is correctly assigned to "New Private Window", where it has replaced the default ⌘⇧P. However, as I said above, the custom key combination doesn't work - it seems to in fact trigger the regular "New Window", which is still the default ⌘N (command+N, no shift key). Any one know if this is a known issue, and if there are any solutions? Using a different key combination is not useful for me, since I'm trying to switch from Chrome and have ⌘⇧N very ingrained in my behavior (I pretty much always use private windows unless I need to log in to a site or explicitly want the history saved). If I can't have ⌘⇧N then I might as well just try to adjust to the default ⌘⇧P. The fact that executing the shortcut brings up a non-private window makes the whole thing much worse - I'm ending up using non-private windows when I think I'm using private ones :/
已附加屏幕截图

所有回复 (4)

more options

Natively, Command+Shift+n is the keyboard shortcut to re-open the last closed window. To test whether it is that or something else, try loading some content into that window and then close the window before using the keyboard shortcut again.

more options

jscher2000 said

Natively, Command+Shift+n is the keyboard shortcut to re-open the last closed window. To test whether it is that or something else, try loading some content into that window and then close the window before using the keyboard shortcut again.

Thanks; I'm already aware of Cmd+Shift+n -> re-open window... the issues is that I want it to open a private window *instead*.

On a user intent level, it seems like custom shortcuts I add should take precedence, but that's not what I'm seeing.

more options

Hi nrser, could you confirm what Command+Shift+n is currently doing with your custom key assignment in place? In other words, is your custom key assignment:

  • being completely ignored -- Firefox is following its native behavior of re-opening the last closed window
  • partially working -- it opens a new window, but of the wrong kind (this would be hard to explain)
more options

This bug is tracked in Bugzilla #1333781

由hongsy2006于修改