Closed Bug 1806948 Opened 2 years ago Closed 2 years ago

alternativeto.net - dark theme not applied automatically

Categories

(Web Compatibility :: Site Reports, defect)

Desktop
All
defect

Tracking

(firefox111 affected)

RESOLVED INVALID
Tracking Status
firefox111 --- affected

People

(Reporter: 08xjcec48, Unassigned)

References

(Blocks 1 open bug, )

Details

Steps to reproduce:

Go to about:preferences#general and set Website appearance to Dark.

Actual results:

https://alternativeto.net/ loads in light mode.

You have to manually click on the icon at the top right corner of the page to enable the dark theme, which sets a Local Storage key. Users who have configured Firefox to delete site data automatically have to keep doing this again every time they open AlternativeTo.

Expected results:

Please reach out to AlternativeTo to ask it to respect prefers-color-scheme.

Blocks: 1591679

I was able to reproduce the issue. Moving the issue to the relevant Product and Component.

Component: Desktop → Theme
OS: Unspecified → Windows 10
Product: Web Compatibility → Firefox
Hardware: Unspecified → Desktop

Raul, this isn't a Firefox bug. As I've explained to you in another issue:

The Website appearance setting doesn't force any site to be dark. It just uses prefers-color-scheme to politely request sites to use their own dark themes, in case they have one.

I've filed this bug for the Web Compatibility team to reach out to AlternativeTo about this CSS feature, as it's been done with Fandom.

Component: Theme → Desktop
OS: Windows 10 → All
Product: Firefox → Web Compatibility

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Well, this isn't a Web Compatibility behavior per-definition, as their behavior is consistent across all browsers.

As I explained in bug 1794320 - which you were also involved in - Mozilla's Web Compatibility team isn't an universal outreach machine to teach people how to improve their web stack. If a site does something that breaks in Firefox but works fine in another browser, that's something we can work on, but we're not going to get into the business of messing with a site's deliberate and consistent code. If you feel strongly about these kinds of issues, then please reach out to the sites yourself.

I sent them an email, but that's all I'm able to do. And just like bug 1794320, I'll close this for the reason I explained above.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID

Emilio was the one who said "We should ask fandom," and then you marked it as a Web Compatibility issue and proceeded to contact Fandom, so I assumed that you'd be willing to send emails to other sites too.

Direct emails from @mozilla addresses are more likely to be read, forwarded to the appropriate employee, and then taken into consideration than the ones that I do send myself.

(In reply to 08xjcec48 from comment #5)

so I assumed that you'd be willing to send emails to other sites too.

Yeah, we can do that in some rare cases. But we simply don't have enough time in the day to do that for all cases.

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