Open Bug 1807088 Opened 3 years ago Updated 4 months ago

Dark mode consistency - UI, initial loading content page color, reader view

Categories

(Firefox for Android :: Design System and Theming, enhancement)

All
Android
enhancement

Tracking

()

People

(Reporter: csadilek, Unassigned)

Details

From github: https://github.com/mozilla-mobile/fenix/issues/16467.

What is the user problem or growth opportunity you want to see solved?

When you use Firefox in dark mode you will have a dark UI which is a specific shade of gray and a loading content page color that is another different shade of gray (this was implemented very recently, see #6313). The shades don't match. If they matched, which is the change I suggest here, Firefox would look more consistent and clean.

Additionally, there's the reader view. You can manually set it to a dark background (by the way, I think the dark background should be automatically selected if the user is using dark mode in Firefox/Android). This dark background is yet another shade of gray different from UI's gray and loading content page's gray. I suggest this color too is unified with those of the UI and the loading page.

How do you know that this problem exists today? Why is this important?

Okay, this is not THAT important, but I see no reason why those three shades of gray should be different from each other. Most likely, they were implemented by different people in different moments, but if they were implemented at the same time in a more "unified" way I'm pretty sure they would have been the same color.
Also, I don't think this is too difficult to fix.

Who will benefit from it?

Dark mode users.

--

Additional pictures ilustrating the issue.

UI's gray.

Initial loading content page color (dark mode).

Reader view's dark background.

Edit:
There's also this other shade of gray from the tab switcher:

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Severity: -- → N/A
Component: General → Design System and Theming
You need to log in before you can comment on or make changes to this bug.