This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can’t select address bar when bluetooth mouse is connected

  • 3 replies
  • 1 has this problem
  • 17 views
  • Last reply by gpd5

more options

I believe this is a bug in Firefox for iPadOS: when a bluetooth mouse or trackpad is connected to the device, if I’m in Firefox and I tap (with my finger) in the address bar to type in a URL or search term, it doesn’t let me change the focus to it. It briefly starts to bring up a keyboard, then that disappears and I’m not given the opportunity to type anything. If I click (with the bluetooth mouse or trackpad) in the address bar, it does then allow me to type.

In almost all other apps, tapping or clicking does the same thing, regardless of whether a mouse is connected at the time.

I believe this is a bug in Firefox for iPadOS: when a bluetooth mouse or trackpad is connected to the device, if I’m in Firefox and I tap (with my finger) in the address bar to type in a URL or search term, it doesn’t let me change the focus to it. It briefly starts to bring up a keyboard, then that disappears and I’m not given the opportunity to type anything. If I click (with the bluetooth mouse or trackpad) in the address bar, it does then allow me to type. In almost all other apps, tapping or clicking does the same thing, regardless of whether a mouse is connected at the time.

All Replies (3)

more options

It seems that, in the scenario described above, if I quickly triple-tap the address bar, the on-screen keyboard does appear. Is that the expected behavior? It seems awfully esoteric.

more options
more options

Done. Bug 1634558