You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
What is the user problem or growth opportunity you want to see solved?
I want the appearance (especially the colouration) of Fenix/Firefox Mobile to adhere adaptively and automatically to what the OS that it is invoked by specifies. Consequently, please support Android 12, 12L, and 13s' Material 3.
How do you know that this problem exists today? Why is this important?
What is the user problem or growth opportunity you want to see solved?
I want the appearance (especially the colouration) of Fenix/Firefox Mobile to adhere adaptively and automatically to what the OS that it is invoked by specifies. Consequently, please support Android 12, 12L, and 13s' Material 3.
How do you know that this problem exists today? Why is this important?
This is important for mere visual consistency and consequent ease of usability for most people, but for many, it supports accessibility, and for OLED devices, the ability that it would gain to present #000000 backgrounds would provide significant improvement (reduction) to usage of power by Fenix.
Who will benefit from it?
Everyone, because implementation of this would not prevent Android versions before 12 using it.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: