Opening new tab via right-click on other tabs doesn't put cursor focus in URL bar
If you have multiple tabs open and you hit Ctrl-T to open a new one, it opens it at the end of the tabs, and the cursor focus moves to the URL bar so you can start typing in an address/search.
If you right-click on any of those tabs, it opens a new tab to the right of that tab, instead of at the end (which is what I want, as right-clicking on a specific one to open a new tab, to me, means you are linking those tabs in layout and want them together) BUT the cursor focus DOES NOT move to the URL bar.
This seems pretty counter-intuitive, and means that so many times I right-click, Open New Tab, and start typing a URL and then see that I have to stop typing, click in the URL bar, and start typing all over again.
Is there an about:config to force the focus to the URL bar, or is this a bug? If there's no setting for this, I would definitely consider this a bug because you have 2 different behaviors for New Tabs.
This is a known issue with container tabs (Bug 1726540), normal tabs are not affected.Read this answer in context 👍 2
All Replies (8)
If I'm understanding you correctly, I can't replicate this behavior. When I right-click a given tab and select New Tab, the new tab opens to the right of the selected tab and the URL bar is automatically selected. I can begin searching or entering a web address immediately.
I will try to get to testing this this weekend on a "new" laptop that doesn't have FF installed on it, to see if I can reproduce it there.
I'll also restart using Profile Mgr on this desktop to a TEST profile and see what happens.
That said, this desktop FF install is less than a month old and doesn't seem to have any other issues. The only real customization is using CSS to enable multi-row tabs, so maybe that is affecting it.
OK, it's looks like the current profile has issues, or the multi-row tab CSS is causing issues.
The "default" profile doesn't have multi-row tabs enabled, and doesn't show the issue. The "TEST-Profile" I just created doesn't have multi-row tabs enabled, and doesn't show the issue.
Working on Troubleshoot Mode next...
Starting the current profile, "default-release" in Troubleshoot Mode result in disabling multi-row tabs, but the issue of the URL bar focus still exists.
I will try to Refresh FF to see if that helps, but I want to document all the changes I've made so I can try adding them back in, and I'm not sure when I will have time to do so.
Hey there! From what you've described, it seems like the behavior might be related to the customization you've done with multi-row tabs. Since you've noticed that the issue doesn't occur in profiles without that customization, it's possible that this specific customization is causing the URL bar focus problem. To fix it, you could try disabling the multi-row tab CSS and see if the issue goes away. If it does, you can gradually reintroduce your customizations to identify the specific one causing the conflict. Remember, starting fresh with a new profile can often help isolate and solve issues.
No, as I noted in my last post:
"Starting the current profile, "default-release" in Troubleshoot Mode result in disabling multi-row tabs, but the issue of the URL bar focus still exists."
So with multi-row tabs not in effect, it still happens on my main profile.
I'll have to investigate further.
"Remember, starting fresh with a new profile can often help isolate and solve issues."
Yes, but it is a HUGE hassle to get a new profile set up like the old one. It's fine if you only need worry about bookmarks and passwords, but there are many other customizations that people do, and getting FF back to looking/acting the way I expect isn't fast or easy.
But it's probably easier than a Refresh, as I can switch between Profiles to get the new set up like the old, until the behavior shows again, which will show whatever finally caused it.
This is a known issue with container tabs (Bug 1726540), normal tabs are not affected.
Thank you, I'll mark it as Solved (even though I won't hold my breath on them solving a P3 that is years old, no matter how trivial it seems the fix might be).