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

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

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

  • 2 amsoshi
  • 0 sa na da wannan matsala
  • 20 views
  • Amsa ta ƙarshe daga Denys

more options

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.
Hoton allon fuska da aka liƙa

All Replies (2)

more options

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.

more options

Hi again,

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

Yi tambaya

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.