-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[BUG] dark mode toggle is not persisted through browser refresh #11593
Comments
@thesuperzapper Thank you for reporting the issue, however, I cannot reproduce the issue. Could you share more about your environment, particularly OS and browser? |
@B-Step62 I am using MacOS, but I just tested and this happens on both Brave (Chrome fork) and Safari, so I imagine it's not related to the browser. Make sure your computer is set to dark mode (in system settings), and then toggle the UI to light mode before refreshing, it should flip back to dark. |
Thanks @thesuperzapper
I can confirm this, while the opposite is not (the dark mode preserves even when system default is light). Are you seeing the latter case as well? |
@B-Step62 you are correct that this only seems to happen when you try and use light mode in MLFlow with dark mode set on your system settings. |
@mlflow/mlflow-team Please assign a maintainer and start triaging this issue. |
I am having the same issue here. |
I am experiencing the same issue. |
Willingness to contribute
No. I cannot contribute a bug fix at this time.
MLflow version
2.11.1
System information
Describe the problem
After every refresh, the dark-mode toggle will default back to whatever your computer's "default preference" is.
For example, if your system is set to dark mode, it will revert to dark.
We should be persisting this in local storage for the domain, so we don't flashbang people after each reset!
Steps to reproduce the bug
Code to generate data required to reproduce the bug
No response
Is the console panel in DevTools showing errors relevant to the bug?
No response
Does the network panel in DevTools contain failed requests relevant to the bug?
No response
The text was updated successfully, but these errors were encountered: