-
Notifications
You must be signed in to change notification settings - Fork 168
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
Styles are not applied when used with auto-entities #184
Comments
I think I might be experiencing the same issue. I am trying to remove a background/make it transparent on a card with auto entities and once the card updates with another entity the background comes back. I am pretty sure its the same issue.
|
There is a problem with card-modding a card inside Example 1 - style is defined for the internal card itself (result OK):
Example 2 - style is defined from the
or
But sometimes even w/o resizing the window etc - just after F5 - the style seems to be applied. So, the problem is about using Since the Another example - with
This does NOT work when using
or
|
just letting you know the update to 3.1.3 does not really help this issue (of the badges What is bit different now, is that I can get the mod to work upon a reload of the view or 2. Before, this didnt work and I needed to resize the screen |
After update, my example with fold-entity-row + auto-entities still gives same unstable results:
Probably the latest update was not purposed to fix this particular behaviour. |
i have to agree with Ildar, and rewriting my auto-entities config in the opening post above to
makes it work immediately. but I guess thats what I already said in the opening post... nevermind, just to stress this is still happening then ;-) |
Marius, the issue should be renamed to "Styles may not be applied when using for auto-entities" probably... |
changed that. thx |
not using this a anymore, but maybe also test the
mod, as that is what the issue was about? tbh, I am not even sure now, this is an auto-entities thing in the first place, though we all believed it was above? |
This is not about a particular CSS property. These "flex" attributes will definitely work (with or w/o !important). |
so are you saying the original issue doesnt exit anymore? |
This is up to you to decide, you are the author. |
yes sure, but what I meant to ask is, if you can confirm the original issue (which you also experienced) is no longer an issue, we can close. |
At least the code I posted here works OK. |
thx. since I dont use the badges from the opening post anymore, nor have any card_mod set directly via any of the other posted examples above (eg using the mod-card), I dont experience this issue anymore, and will close. thanks for taking part |
My Home Assistant version: 2022.4.0.dev20220228
My lovelace configuration method (GUI or yaml): YAML
What I am doing:
showing badge card which is auto-filled by auto-entities and justify the badges
What I expected to happen:
immediate effect (as before, somehow latest are releases frustrate correct operation)
What happened instead:
need a resize window in the browser to have the mod be effective, ast least showing the mod is ok.
Minimal steps to reproduce:
using a fixed set of badges:
always works, proving the mod to be correct
Error messages from the browser console:
no errors
By putting an X in the boxes ([]) below, I indicate that I:
Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
Have made sure I am using the latest version of the plugin.
Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
The text was updated successfully, but these errors were encountered: