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.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

How to access the location bar via BT keyboard? (ctrl-l does not work)

  • 1 reply
  • 11 have this problem
  • 1 view
  • Last reply by Kevin

spaetz
spaetz
more options

Having a full fledged bluetooth keyboard connected to my Android tablet, I cannot really use it nicely with Firefox, as there is no way to reach the location bar via keyboard. Ctrl-L as it works on the desktop does not seem to work on the Android tablet.

Is there a different key combo to achieve this, has it been overlooked (as it is normally not available on Android), or am I missing something obvious?

Having a full fledged bluetooth keyboard connected to my Android tablet, I cannot really use it nicely with Firefox, as there is no way to reach the location bar via keyboard. Ctrl-L as it works on the desktop does not seem to work on the Android tablet. Is there a different key combo to achieve this, has it been overlooked (as it is normally not available on Android), or am I missing something obvious?

Chosen solution

There is support for keyboard shortcuts for text entry. However you are correct that shortcuts such as ctrl + l do not function. We have an open issue on this feature but don't have a timeline for implementing it.

Read this answer in context 👍 0

All Replies (1)

Kevin
Kevin
  • Moderator
more options

Chosen Solution

There is support for keyboard shortcuts for text entry. However you are correct that shortcuts such as ctrl + l do not function. We have an open issue on this feature but don't have a timeline for implementing it.