Keyboard shortcut for "open focused link in new tab" (alt-enter) doesn't work.
Categories
(Firefox :: Keyboard Navigation, defect)
Tracking
()
People
(Reporter: reganwieland, Unassigned, NeedInfo)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
Hit Command-Enter to open focused link in new tab.
Actual results:
Nothing
Expected results:
Open focused link in new tab.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Keyboard Navigation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Reganwieland, could you give more details about the issue you are experiencing? Are you trying to open the focused link from the Address bar?
Please see also Bug 1670484.
| Reporter | ||
Comment 3•3 years ago
|
||
Until most recent update, I've been able to open a hovered-over link in a new background tab by hitting Command-Enter on my Mac keyboard. This is no longer working, Command-Enter now has no resulting action at all.
Comment 4•3 years ago
|
||
(In reply to reganwieland from comment #3)
Until most recent update, I've been able to open a hovered-over link in a new background tab by hitting Command-Enter on my Mac keyboard. This is no longer working, Command-Enter now has no resulting action at all.
I can't reproduce this - I can still open links in a new background tab (with Command + Enter) when focusing that link via the keyboard (I reach the link by clicking the Tab key) — tried on the latest Nightly 107.0a1 and Firefox 105.0.3 on macOS 11.6.
To avoid the influence of any addons or customed settings, could you please check if you are having issues opening the focused tabs by running Firefox in safe mode or with a new profile?
http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Comment 5•3 years ago
|
||
Closing as Resolved: Incomplete due to no update from the reporter. If anyone can still reproduce this issue, please feel free to reopen the bug. Thanks!
Description
•