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!

Avatar for Username

ابحث في الدعم

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

This thread was archived. Please ask a new question if you need help.

About:Cofig not saving and the new layout

  • 1 (رد واحد)
  • 1 has this problem
  • 1 view
  • آخر ردّ كتبه cor-el

oblic008
oblic008
more options

I HATE the new look. I've hated it ever since they smoothed everything out, and tabs just look like some sort of continuous amorphous mess. I want the lines between tabs so it is easier to distinguish between them. I know that changing the "browser.proton.enabled" to false gets rid of this garbage new look, but for some reason, whenever I switch this over, the setting doesn't save. Every time I reopen FireFox, it reverts back to this ABSOLUTELY TERRIBLE layout. (can you tell I hate it? FIX IT MOZILLA!!!!)

Please help...?

Thanks!

I HATE the new look. I've hated it ever since they smoothed everything out, and tabs just look like some sort of continuous amorphous mess. I want the lines between tabs so it is easier to distinguish between them. I know that changing the "browser.proton.enabled" to false gets rid of this garbage new look, but for some reason, whenever I switch this over, the setting doesn't save. Every time I reopen FireFox, it reverts back to this ABSOLUTELY TERRIBLE layout. (can you tell I hate it? FIX IT MOZILLA!!!!) Please help...? Thanks!

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The "browser.proton.enabled" is no longer supported and is best left at its default value (true) to avoid weird issues as it can still have some effects.

It is only possible to override/revert changes coming with the Proton design by using code in userChrome.css.

DISCLAIMER: modifications made through a userChrome.css or userContent.css file can stop working as Firefox evolves in new releases, and can "break" Firefox in serious ways.