You are right the reason i deleted my post is because it didnt give the effect you wanted which was dynamic sizing. Setting it to 0 just got rid of the entire section.
$
i used when an object has a shadow root and you want to access the element inside that shadow root. So here the #calendar
element is inside the shadow root of the ha-full-calendar
element so we add a $
to account for that.
If we just wrote:
card_mod:
style:
ha-full-calendar: |
#calendar {
min-height: 300px !important;
}
It would not work as the #calendar
element is not inside the ha-full-calendar
element, its inside the shadow root of ha-full-calendar
you can basically start with any element as long as you dont hit a shadow root. if you hit a shadow root you need to start with that element and drill down.
so for example if am wanting to change the text of an entity card. i am already inside the ha-card (because my card_mod is applied to the card itself) so we can ignore the shadow root for that. i can then see that .value is is inside .info but i dont need to declare it, because .value is not inside the shadow root of .info. so this works:
card_mod:
style: |
.value {
color: red !important;
}
but lets say i have an entity card where i want to modify the ha-svg-icon
instead (could probably just change the ha-state-icon
instead, but stay with me). now shadow roots are involved so therefore i now need to declare this:
Notice that i can ignore anything after ha-card up until i get to ha-state-icon, because none of it is in a shadow root.
card_mod:
style:
ha-state-icon$: |
ha-svg-icon {
color: red !important;
}
as this will not work. because ha-svg-icon
is inside the shadow root of ha-state-icon
card_mod:
style: |
ha-svg-icon {
color: red !important;
}