We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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

  • 1 відповідь
  • 11 мають цю проблему
  • 1 перегляд
  • Остання відповідь від 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?

Обране рішення

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.

Читати цю відповідь у контексті 👍 0

Усі відповіді (1)

Kevin
Kevin
  • Moderator
more options

Вибране рішення

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.