Closed Bug 1953990 Opened 11 months ago Closed 10 months ago

ctrl+enter shortcuts triggers autocompletion to .com address instead of opening the address in a new tab

Categories

(Firefox :: Address Bar, defect)

Firefox 136
defect

Tracking

()

RESOLVED DUPLICATE of bug 1949999

People

(Reporter: waynejwoww, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

type an address/search term in the urlbar and hit ctrl+enter.

Actual results:

the address/search term is autocompleted to a .com address and isn't opened in a new tab.

Expected results:

the address/search term should not be autocompleted and opened in a new tab.

it is not 1998 anymore. a lot of websites do not use ".com" as tld anymore. firefox is a globally used product. the prevalence of ".com"-addresses differs vastly from region to region. a prominent shortcut like ctrl+enter should not be occupied by such an outdated feature.

autocompletion-suggestions are triggered anyways, so in most cases the addres will anyways be completed to .com and subsuequently can be opened by just hitting enter.

in addition: a lot of other tab related shortcuts use the ctrl key as modifier:
ctrl + tab : change tabs
ctrl + t : open new tab
ctrl + F4 : close tab
ctrl + w : close tab
Ctrl + Page Down : Go one Tab to the Right
Ctrl + Page Up : Go one Tab to the Left
Ctrl + Shift + Page Up : Move Tab Left
Ctrl + Shift + Page Down : Move Tab Left

assigning alt+enter to open an address/search term from the urlbar in a new tab is extremely counterintuitive.

please also implement customizable shortcuts

The Bugbug bot thinks this bug should belong to the 'Firefox::New Tab Page' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → New Tab Page
Component: New Tab Page → Search
Component: Search → Address Bar
Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Duplicate of bug: 1949999
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.