Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

The settings gear for the sidebar is situated near the top instead of the bottom

  • 2 svar
  • 0 har detta problem
  • 31 visningar
  • Senaste svar av Denys

fler alternativ

I really enjoy the new sidebar revamp, but I've had an issue with it recently that I haven't been able to find a solution for. Typically, the settings gear is supposed to be situated near the bottom of bar. However, as demonstrated in the attached image, it is at the top near the bookmarks and history buttons. I have tried reinstalling the browser from scratch, turning the sidebar on and off, turning vertical tabs on and off, and even getting rid of my custom CSS theme for a time. None of these have worked. If anyone knows what the root of this issue is, I'd really appreciate the help.

I really enjoy the new sidebar revamp, but I've had an issue with it recently that I haven't been able to find a solution for. Typically, the settings gear is supposed to be situated near the bottom of bar. However, as demonstrated in the attached image, it is at the top near the bookmarks and history buttons. I have tried reinstalling the browser from scratch, turning the sidebar on and off, turning vertical tabs on and off, and even getting rid of my custom CSS theme for a time. None of these have worked. If anyone knows what the root of this issue is, I'd really appreciate the help.
Bifogade skärmdumpar

Alla svar (2)

fler alternativ

Hi,

Thank you for reaching out! That turned out to be a bug. After you raised this issue, a report has been filed, and I hope it will be fixed soon.

I'll keep you updated. If you want, you can also follow the issue under the link.

fler alternativ

Hi again,

Sorry for reaching back a bit late, but the issue should have been resolved with Firefox 144.0.2 release!

Ställ en fråga

Du måste logga in på ditt konto för att svara på inlägg. Vänligen starta en ny fråga om du inte har ett konto ännu.