Check two PRs of dcapslock which broke styles for entities card. Changing Frontend in favor of card-mod…
Why not provide urls to these " Resentful " accusations , i mean that is your point , right … provide a solution/cause to the " Issue "
1 Like
Why not opening pull requests on GitHub and filter?
Don’t find those PRs in the repo.
https://github.com/iantrich/config-template-card/pulls
Can you gibe more details?
In ha frontend repo.
He proposed changes for padding-top which caused its removal under some conditions. And it mainly touched when Entities card was wrapped into another card.
Hm. But then I cannot see a help for me, only the reason, can I? That there was a change, I saw it. I search for help to fix it in this card. If there were a PN in the repo of the this card, I would appriciate much, because I would be able to adapt without a release. But changes in frontend, no, I cannot fix it.
For now, you will have to use cardmod. I may propose a fix in ha frontend - but I very doubt that I can explain it by “custom card does not work”. Need to figure out a way of another fix…
But thanks for the hint. As this is the only card in my HA, then I will modify the card source to bring back fixed padding top and then it is working without card-mod.
Arganto, can you check if other cases are affected?
Restriction card, tabbed-card, stack-in-card.
For restriction card I don’t see problems in my dashboards. Tabbed card not in use. Stack in card neither. Still using a modified vertical-stack-in-card.
The padding top is missing only when the Entities card has no title. Will check again how to mitigate this. The initial PR was definitely not thoroughly reviewed.
1 Like
Btw, meanwhile there is a workaround for you.
Use CTC for a ROW.
Also, Arganto, can you check with card-mod 3.x?
What to check? If it is a frontend change problem. Ofc I would be able to set the padding, but I don’t want this. Will try via row.
It could be related to “card_mod” element automatically prepended. A need to place this element in the beginning of DOM structure was a reason why those mentioned PRs were issued. That is why I suggested you to check with 3.x. I could do it myself, I am just away from a PC, that is why I am asking you, sorry!
I am not replicating this. Can you see if clearing Frontend cache helps?
For transparency for this discussion, the 2 PRs referred to are Fix ha-card styling of .card-content when not first element but not following .card-header by dcapslock · Pull Request #28935 · home-assistant/frontend · GitHub and Fix CSS minification issue for ha-card by dcapslock · Pull Request #29354 · home-assistant/frontend · GitHub, the 2nd PR being required due to a CSS minification bug with the CSS minification tool being used by Home Assistant.
The first PR updates the CSS for ha-card such that the .card-content class only sets no top padding and negative margin when it is not the first element of .card-content or .card-header. Before this it was setting if not first child, giving rise to an issue if any other element made its way into DOM, card-mod auto prepend or otherwise.
What you show suggests that its a combination of card-mod 4.2.x and old frontend CSS for ha-card being used, which is not expected, hence the request to clear Frontend cache.
If there is any issue with Frontend PRs submitted by myself, I will provide follow up and resolution if required. Case in point being the 2nd PR being a third party tooling bug which took many hours to uncover and which I expidited prior to final release of 2026.2.0.
1 Like
No, it is not a cache topic: HA 2026.1.3 with card-mod 4.2.1
But I changed now to ROW-approach and this solved to problem. Thanks again Ildar for the hint.
1 Like
Confirming you are running 2026.1.3?. Card-mod 4.2.0+ requires Home Assistant 2026.2.0 or above for 2 reasons. 1) Specifically this issue so the updated ha-card CSS is used and 2) For yaml theme loading due to the developer tools route change.
Yes. As discussed in the other topic. HACS did the update without a blocking.
But as said. Solved with row-option and currently I’m in that way blocked, that I cannnot test other approaches. But thanks again for your help as well.
1 Like
Thank you for confirming as it explains why you were having the padding issue.