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!

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Enable dark theme for UI without forcing it on websites?

  • 2 wótegronje
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót cor-el

Raynor
Raynor
more options

I don't understand why Firefox Android was designed so that the UI's dark theme also gets automatically thrust upon websites without user consent?

Dark theme for the UI and dark conversion for websites are supposed to be two *different* features. It baffles my mind that they were merged together like this, rather than just add an extra toggle for the user.

I know that there's an option to un-toggle the websites going dark in the about:config menu. But the Firefox stable release has actually disabled access to about:config as well!?

So what are we left to do? Just forever use the Beta/Nightly versions if we want any customizability over our favorite browser?

Why even disable about:config in the stable release in the first place, generally speaking? Chrome doesn't disable access to it in their stable release versions. Who's brilliant idea was it to make this change?!

I don't understand why Firefox Android was designed so that the UI's dark theme also gets automatically thrust upon websites without user consent? Dark theme for the UI and dark conversion for websites are supposed to be two *different* features. It baffles my mind that they were merged together like this, rather than just add an extra toggle for the user. I know that there's an option to un-toggle the websites going dark in the about:config menu. But the Firefox stable release has actually disabled access to about:config as well!? So what are we left to do? Just forever use the Beta/Nightly versions if we want any customizability over our favorite browser? Why even disable about:config in the stable release in the first place, generally speaking? Chrome doesn't disable access to it in their stable release versions. Who's brilliant idea was it to make this change?!

Wšykne wótegrona (2)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

You are welcome to provide feedback directly to our developers about the theme options. If you want to leave feedback for developers, you can go to the Firefox Help menu and select either Share ideas and feedback… or Submit feedback…, depending on your Firefox version. Alternatively, you can use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.

With regards to about:config, it does not give access to as many options as initially appears as many are baked into the GeckoView engine when the app is compiled. Additionally to this, there is also a very high risk of losing all data stored in Firefox for Android. As such, it was thought better to limit the availability to testing and developer users.

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

Note that in the desktop release version you do not need to use about:config, but can do this via "Settings -> General -> Language and Appearance -> Website Appearance".