Closed Bug 1745220 Opened 2 years ago Closed 2 years ago

Firefox 95 (on Mac OS Sierra 10.12.6) with a "dark theme" shows many sites with dark themes automatically - bug or intended behaviour?

Categories

(Firefox :: Theme, defect)

Firefox 95
defect

Tracking

()

RESOLVED DUPLICATE of bug 1736218

People

(Reporter: jonbonjovi886, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:95.0) Gecko/20100101 Firefox/95.0

Steps to reproduce:

I just open sites like Twitter, Youtube, Google search results

Actual results:

If you set a "dark" theme in Firefox 95, many websites show their dark mode automatically instead of their "light" version of the pages, for example Youtube is dark, Google search results too, Twitter too... etc...

Expected results:

I want to be able to choose if I want the dark mode in websites pages, not displayed automatically if my browser has a "dark" theme or not considered "light" theme. I want light mode instead without having to apply a browser's "light" theme

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Widget: Cocoa
Product: Firefox → Core

The dark/light theme for websites (those that respect prefers-color-scheme) is now based on the browser theme and not the OS, this was intentionally changed with bug 1529323. Bug 1736218 is about adding some UI to change whether websites/content see dark or light.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Component: Widget: Cocoa → Theme
Product: Core → Firefox
Resolution: --- → DUPLICATE

I think this should be a choice, for instance I don't want to see the dark themes in webpages, even if I have a "dark" theme on my browser.

Anyway I set this preference in about:config :
"layout.css.prefers-color-scheme.content-override" to 2 and that's how I like it to be.
Even if I see the Preferences in white now. But I want the light themes on webpages ;)

You need to log in before you can comment on or make changes to this bug.