-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dark Mode not working #1
Comments
Is your system theme set to dark? |
Yes |
System theme, not Firefox theme |
The dark mode is just a simple |
Also, which addons are you running? |
Dark Reader may sometimes interfere |
Running Ublock Origin and DarkReader, although I disabled the latter for the time being. |
Well, I implemented the dark mode the simplest possible way, so there may be a bug in the fork of Firefox you're using |
What Android version are you on? |
Latest Android 13 for the Galaxy Tab S8 |
I'm also on a Samsung device, but it works for me. |
Hi, same issue with same configuration of Mull. Do you think it may be possible to add a dark mode switch in the extension setting? |
I think the issue is caused by an about:config setting in Mull which, aiming to increase privacy, hides the true value of prefers-color-scheme media query to websites. Since the addon is running inside of an iframe, on a website, it is impacted by this too. The reason why I didn't ship a JS powered dark mode was to avoid flashes of white before settings are received by the tab bar iframe, and the proper color would be set. So I could implement a dark mode, but if I send settings to a tab from a background script (where they are loaded in RAM), it is still slow enough for the user to notice. So if you have any hack/idea how to retrieve that dark mode setting faster, that would be nice |
The Manifest V3 session storage API looks promising (as its all in memory, can be done as shared memory, so it should be fast), but then I'd have to rewrite the entire thing to Manifest V3, which would probably add random slowness since background scripts are not allowed to be persistent in MV3, meaning once the background script is forcibly turned off, the user would send an event from the tab bar, which would wake up (start) the background script, which would then execute what's needed. It would basically have to be loaded from the disk, compared to being loaded in memory all the time right now (MV2) |
Perhaps an interesting quick fix for you is considering Dark Reader. Apart from giving all websites a nice color scheme, it also gives the tab bar a dark mode (even when the tab bar is set to light mode by Android's theme setring.), solving the situation. |
The Dark mode is not working for me even though I have selected it in Firefox settings.
Galaxy Tab S8 with Mull.
The text was updated successfully, but these errors were encountered: