Open Bug 1796381 Opened 2 years ago Updated 8 months ago

New Tab does not auto-focus Address Bar


(Firefox :: Address Bar, defect, P3)

Firefox 106





(Reporter: tokillthebug, Unassigned)



Steps to reproduce:

  1. Right-click an existing tab.
  2. Choose: New Tab

Actual results:

A new tab opens, but the address bar did not receive keyboard focus automatically.

Expected results:

After the new tab opens, the address bar should automatically receive keyboard focus.

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

Component: Untriaged → Address Bar

106.1 resolves this issue for me.

Closed: 2 years ago
OS: Unspecified → Windows
Hardware: Unspecified → Desktop
Resolution: --- → WORKSFORME

Spoke too soon. The same issue remains in 106.1. Heisenbug territory.

Resolution: WORKSFORME → ---

Thank you for your report.

I tried to reproduce this issue using both Firefox 106.0.1 and latest Nightly 108.0a1 under Win 10 64-bit.
For me, the address bar is focused when switching to a new tab, but please note that the cursor only blinks for a few seconds (this is set at system level, is not a Firefox setting). Same thing happens when opening a new tab with Ctrl+T or by using the + button in the toolbar.

If that's not the case for you, please let us know:

  • Which system are you using?
  • Does it reproduce with a clean profile?
  • What's happening when you start typing right after the new tab is opened?

Thank you!

Flags: needinfo?(tokillthebug)

I normally use Ctrl-T, but I recall using New Tab or the + button didn't make any difference when I observed the issue during 106.0.

Q: Which system are you using?
The PC that is experiencing this issue is running Windows 7 x64.

Q: Does it reproduce with a clean profile?
I haven't seen a reason to try because it happens so infrequently after 106.1 (across multiple instances, all using different profiles).

  • Always use private browsing mode is enabled for all profiles (which I understand should disable the new "Firefox View" feature).

Q: What's happening when you start typing right after the new tab is opened?

  • If the address bar gets keyboard focus, it has a border around it, and I can enter text directly, as I'd expect to.
  • If the address bar doesn't get keyboard focus, it doesn't have a border around it, and it takes me a second to realize it doesn't receive key strokes, and I have to Alt-D or click it to give it keyboard focus.

In summary, my experience is that 106.0 consistently reproduced the issue, 106.1 rarely manifests the issue, pre-106 never had the issue.

Flags: needinfo?(tokillthebug)

100 % reproducible if we open a new tab by right-clicking any open tab, and choosing "New Tab" from the menu. Same results when opening the profile using troubleshooting mode.

Reminder: All profiles used so far have "Always use private browsing mode" enabled (search for it in Settings).

I wasn't able to reproduce the described behavior on Win 7 (32-bit) or Win 10 (64-bit) using both Normal Mode and Persistent Private Browsing Mode and all the ways to open a new tab (with focus on the contextual menu).

Would you please help us into finding the bug that introduced this behavior for you? You have to install mozregression from here and execute the builds it provides (good = 105 / bad = 106).

Thank you!

Flags: needinfo?(tokillthebug)

It's Win 7 SP1 (64-bit/x64).

I completed the installation of mozregression-gui.exe, but it fails to start with a fatal error. There's no antivirus blocking it from running.

I've seen this message before when developers build executables using Win 10 specific APIs (which won't work when run under Win 7).

These two dialogs pop up when mozregression-gui.exe starts, in order.

mozregression-gui.exe - System Error

The program can't start because api-ms-win-core-path-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.


Fatal error detected

Error loading Python DLL 'C:\Program Files (x86)\mozregression-gui\python310.dll'.
LoadLibrary: The specified module could not be found.


Flags: needinfo?(tokillthebug)

Looking through the C:\Program Files (x86)\mozregression-gui\ directory, there are many api-ms-win-core-* files, but api-ms-win-core-path-l1-1-0.dll is missing.

python310.dll is present.

The version I installed was updated two days ago (5.1.0).

106.0.2 does not fix this issue.

106.0.3 does not fix this issue.

No response to bug #1797537.

The severity field is not set for this bug.
:adw, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(adw)

I have the same bug with Nightly build on MacOS, the thing is to reproduce a bug you need to have browser opened in full screen mode. If it's in windowed it works fine. Maybe it's the same with Windows.

If this is a regression I suspect bug 1565751, which landed in 106, and it might be fixed by bug 1801060.

Severity: -- → S3
Flags: needinfo?(adw)
Priority: -- → P3
See Also: → 1565751, 1801060

Open a new tab.
Click anywhere on the page to make sure it's selected.
Press the "Tab" key on your keyboard This should move the focus to the address bar.
If this doesn't work, consider checking your Chrome extensions. Some extensions might interfere with the default behavior. Try disabling extensions one by one to identify if any of them are causing the issue.

You need to log in before you can comment on or make changes to this bug.