Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Can't open first pinned tab when FF window maximized

  • 2 odgovora
  • 0 ima to težavo
  • 4 ogledi
  • Zadnji odgovor od ozhamlet

ozhamlet
ozhamlet
more options

When FF (113.0.1) is maximized clicking on the first (left hand) pinned tab does not open the tab. Hovering over the tab doesn't change the background color of the tab.

If I restore down the window, hovering over the tab changes the background color of the tab from light grey to a slightly darker grey and clicking the tab opens it.

When FF (113.0.1) is maximized clicking on the first (left hand) pinned tab does not open the tab. Hovering over the tab doesn't change the background color of the tab. If I restore down the window, hovering over the tab changes the background color of the tab from light grey to a slightly darker grey and clicking the tab opens it.

Izbrana rešitev

This problem persisted for several days including earlier today but seems to have resolved. It's now working. Still the same version number so not sure what has happened.

Preberite ta odgovor v kontekstu 👍 0

Vsi odgovori (2)

ozhamlet
ozhamlet Lastnik vprašanja
more options

A workaround is to use the tab dropdown list at the right hand end of the tab bar to select the left hand pinned tab.

ozhamlet
ozhamlet Lastnik vprašanja
more options

Izbrana rešitev

This problem persisted for several days including earlier today but seems to have resolved. It's now working. Still the same version number so not sure what has happened.