Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Searching through the adress-bar opens new Tab.

  • 1 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 12 gösterim
  • Son yanıtı yazan: Fortorin

more options

A few moths ago, when you visited a website and then typed some new search-term in the address-bar, you used to be able to search right in that tab. Now a new tab opens up and you get moved there.

While programming, i search for a lot of stuff. Switch to Firefox -> Ctrl+L -> type search-term is the fastest way i found to search for whatever I need. Problem is: now my browser clutters itself by always opening new tabs instead of just reusing the one i don't need anymore.

So my questions would be this:

  1. Is it possible to restore the old behaviour of staying within your one tab?
  2. If there is some other shortcut that allows for searching without moving to a new tab?

(I also tried Ctrl+K and Ctrl+J. Both still open a tab when you already are on a website.)

A few moths ago, when you visited a website and then typed some new search-term in the address-bar, you used to be able to search right in that tab. Now a new tab opens up and you get moved there. While programming, i search for a lot of stuff. Switch to Firefox -> Ctrl+L -> type search-term is the fastest way i found to search for whatever I need. Problem is: now my browser clutters itself by always opening new tabs instead of just reusing the one i don't need anymore. So my questions would be this: # Is it possible to restore the old behaviour of staying within your one tab? # If there is some other shortcut that allows for searching without moving to a new tab? (I also tried Ctrl+K and Ctrl+J. Both still open a tab when you already are on a website.)

Tüm Yanıtlar (1)

more options

Related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1650209

Still looking forward to this finally getting fixed.