Showing questions for topic:
מוצגות שאלות עם התגיות:

Mozilla's forced white backgrounds on support.mozilla.org and accounts.firefox.com cause physical eye pain and migraines, and you removed all user overrides

I have albinism. Pure white backgrounds are not an annoyance – they cause physical eye pain and trigger migraines. Every time I visit support.mozilla.org or accounts.fire… (read more)

I have albinism. Pure white backgrounds are not an annoyance – they cause physical eye pain and trigger migraines. Every time I visit support.mozilla.org or accounts.firefox.com, I am forced to endure #FFFFFF with no way to change it.

To anyone about to defend Mozilla blindly: this is about accessibility and eye pain, not brand loyalty, so do not silence me.

What Mozilla has done:

  • Disabled extensions (Dark Reader, Stylus, Dark Mode) from modifying these pages – they are explicitly blocked by Mozilla's own Content Security Policy.
  • Removed ui.systemUsesDarkTheme and layout.css.prefers-color-scheme.content-override from having any effect on these sites – they ignore prefers-color-scheme entirely.
  • Left no about:config toggle to disable the forced light theme.

The only remaining workaround is a userContent.css hack with filter: invert(1) – which requires a visually impaired user to manually edit CSS files and restart the browser. That is not accessibility – that is hostility.

Security excuse – debunked:

  • "We block extensions for security" – extensions are sandboxed. Blocking them on your own support pages is a deliberate policy choice, not a technical necessity.
  • "We want a consistent brand appearance" – branding does not override accessibility. Forcing #FFFFFF on users with light sensitivity is a violation of basic inclusive design.
  • "We respect prefers-color-scheme" – you do not. These two domains explicitly override it.
  • "Users can just use Dark Reader" – you block it.

What I demand:

Make support.mozilla.org and accounts.firefox.com respect the system prefers-color-scheme media query. If you insist on light branding, add an official dark toggle in the site header – stored in a cookie or account preference. Stop blocking extensions from applying user‑chosen themes to your own sites. That is not security; it is control. You are a non‑profit that claims to value accessibility and user control. Your actions say otherwise. Fix these two domains. No CSS hacking should be required for basic vision safety.

נעולה 15

Are there any shortcuts planned for split view?

I find the new split view feature to be great, however I do find some basic keyboard shortcuts missing. Things like: Focusing the other view Closing a view Splitting Woul… (read more)

I find the new split view feature to be great, however I do find some basic keyboard shortcuts missing.

Things like: Focusing the other view Closing a view Splitting

Would be great to have these basic ones.

נפתרה 3 307

Firefox dark mode(s) lack contrast in context menus on ChromeOS

When using any dark Firefox theme on ChromeOS, the contextual menu text and background are both dark. This means there is little to no contrast, and so the text is very d… (read more)

When using any dark Firefox theme on ChromeOS, the contextual menu text and background are both dark. This means there is little to no contrast, and so the text is very difficult to read.

Unfortunately, the ChromeOS screenshot tool doesn't work on Linux apps, and so I'm unable to share a screenshot. Tested using several dark themes, including the default -- behaviour was consistent in all.

Firefox installed using the official package through the built-in ChromeOS Linux VM "crostini". Issue has been reported by other users on other platforms in the past, so this seems to be a long-standing bug.

Archived 1 180