Add ability to use the new non-native theming implementation using the `widget.disable-native-theme-for-content` pref
Categories
(Core Graveyard :: Widget: Android, enhancement)
Tracking
(firefox81 fixed)
| Tracking | Status | |
|---|---|---|
| firefox81 | --- | fixed |
People
(Reporter: spohl, Assigned: spohl)
References
Details
Attachments
(2 files)
The idea is to move the original, currently active implementation of non-native theming for Android to nsNativeThemeAndroid to mirror behavior on platforms where we have native theming. We can then use the widget.disable-native-theme-for-content pref to enable the new non-native theming implementation.
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
Adding n-i in case Phabricator didn't properly notify you of the questions there.
|
||
Comment 3•4 years ago
|
||
Whoops, sorry, I had missed, thanks for the ni :)
You are not changing behavior but are changing whether the nativeThemePref reftest annotation matches. For example, you need to change this line to be random-if(gtkWidget||Android) and such.
|
|
||
Comment 4•4 years ago
|
||
Or do || sandbox.Android here, but that may be not great because then you have no way to differentiate the old and new non-native theme.
|
|
Assignee | |
Comment 5•4 years ago
|
||
|
||
Comment 7•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/30d39d5782d8
https://hg.mozilla.org/mozilla-central/rev/dd3a1cf66864
|
||
Updated•3 years ago
|
Description
•