-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Map card, new contrasted design: the "the dark_mode" option does not work #13333
Comments
Another explanation. If the system theme is set to Dark as opposed to Auto or Light, the Map Card, Dark Mode ? toggle switch has no effect on the map theme. It remains in Dark mode theme. If the system theme is set to Light, then the Dark Mode ? toggle switch does change the map theme between Light or Dark. |
Is it your explanation of THE CURRENT implementation or is it your proposed implementation? If 1st: |
This is the current method of operation which is incorrect. Dark mode is selected as main theme. |
Note that in dark theme the un-toggled "dark_mode" makes the map more contrasted. |
Yes, but that is not the correct function of the toggle switch. It's being mis-used. |
I described the expected behaviour in the 1st post. |
I suggest you re-read your 1st post. It's not at all clear what you are trying to achieve from it. |
The dark mode toggle only works if you are in light mode and want to have the map dark. No other functionality is offered. |
Then the toggle should be removed if you are in dark mode. |
This was the previous functionality which does not work now: Isn't it? Update: Strange, the logic here is: Really strange. Results of tests in 2022.7.4 are below:
|
As a programmer with 48 years of experience, the toggle should not have been changed. The whole purpose of this update was to first change the Light theme to a more colorful presentation which has been acheived by updating the Leaflet OpenStreetMap. |
This is a Feature Request not an issue. |
What exactly is a FR? The "dark theme / dark_mode=false" is DIFFERENT.
But even when comparing 2022.7.4 & 2022.8, what I see is: |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
up |
it should be possible to choose a light theme for the map, when the main theme is dark |
up |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
up |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
up |
It's impossible to have white map with dark app interface. This is a bug, that should be fixed. Recent activity is not a reason to ignore it, please disable auto-closing. |
It makes sense that, if a user doesn't define a dark_mode setting, the map card follows the theme setting, but if the user specifically specifies dark_mode: false it surely makes sense to respect that? Why not do so? |
Fixed by #20541 |
Checklist
Describe the issue you are experiencing
On 2022.8 a new "more contrasted" design was provided for Map card.
The
dark_mode
option now works not as it did earlier.Here is how it works now:
Light default theme:
The bottom map is dark (why?).
Dark default theme:
The upper map is dark (why?).
The bottom map is less dark (why?).
The upper map is dark (why?).
Describe the behavior you expected
If the
dark_mode
istrue
then:If the
dark_mode
isfalse
or not specified then:Steps to reproduce the issue
As described above.
What version of Home Assistant Core has the issue?
2022.8.0
What was the last working version of Home Assistant Core?
2022.7.7
In which browser are you experiencing the issue with?
Chrome 103.0.5060.134
Which operating system are you using to run this browser?
Win10x64
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: