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!

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Can't open first pinned tab when FF window maximized

  • 2 antwoorde
  • 0 hierdie probleem
  • 28 views
  • Laaste antwoord deur 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.

Gekose oplossing

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.

Lees dié antwoord in konteks 👍 0

All Replies (2)

ozhamlet
ozhamlet Vraag-eienaar
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 Vraag-eienaar
more options

Gekose oplossing

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.