-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Loading screen shows white background in dark mode #6607
Comments
Is your device in dark mode or have you manually set dark mode? |
The device is in dark mode (iPhone/iPad) |
The same for me on Windows 10 and Android 10 on Samsung. Dark mode enabled on both operating systems. |
@ludeeus The flash happens for me before that loading screen is shown (Firefox on Win 10). Once I see the "Loading data" text and the progress ring, it has the proper black background. But at least for me the flash exists with all themes (HA default white as well as 3rd party ones). With dark ones such as HA default dark it is just more visible and more jarring. |
I played around a bit with manually triggering a page refresh in Firefox and then immediately pressing stop in Firefox. I then ended up on the following white page ( Note: The text "Unable to connect to Home Assistant" is in the DOM, but is rendered white, |
It is because we add our default styles before we load the selected user theme/dark theme. https://github.com/home-assistant/frontend/blob/dev/src/entrypoints/app.ts#L3 |
Yes, I had played around a bit by setting => So is that something that falls in the category "cannot / won't solve" or do you see an option to adjust here something? |
I found a way how to prevent the white flashes. PR is coming in the next minutes. |
This PR #6815 fixes the flashing for the main content area. |
Checklist
The problem
Expected behavior
Background of the page to be black/ gray if the theme is set to dark mode
Steps to reproduce
Environment
State of relevant entities
Problem-relevant configuration
Javascript errors shown in your browser console/inspector
Additional information
The text was updated successfully, but these errors were encountered: