You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated to the latest available Home Assistant version.
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
Card heights are inconsistent when using precise mode.
In both pictures below, precise mode is being used and YAML editing is used. Columns is set to 4 (so that there is 3 cards across). Value for rows varies. For each picture the first card has rows: 2, the second card has rows: 1, and the third card has rows: (value for rows is blank).
Note that when the rows key is removed from the YAML it appears to always treat is as rows: 2. None of the cards in the pictures show the configuration with the rows keyword removed.
Describe the behavior you expected
For the tile card example I expect that rows: behavior is well defined. I like the current behavior but feel uneasy building a dashboard based on this behavior because it is not well-defined. I want the more compact view for my cards.
For the template card example I suspect that the second card is a Mushroom bug. For the third card I have the same concern as above.
Steps to reproduce the issue
For the first picture the following YAML is used, varying rows as described above:
Checklist
Describe the issue you are experiencing
Card heights are inconsistent when using precise mode.
In both pictures below, precise mode is being used and YAML editing is used. Columns is set to 4 (so that there is 3 cards across). Value for rows varies. For each picture the first card has
rows: 2
, the second card hasrows: 1
, and the third card hasrows:
(value for rows is blank).Note that when the
rows
key is removed from the YAML it appears to always treat is asrows: 2
. None of the cards in the pictures show the configuration with therows
keyword removed.Describe the behavior you expected
For the tile card example I expect that
rows:
behavior is well defined. I like the current behavior but feel uneasy building a dashboard based on this behavior because it is not well-defined. I want the more compact view for my cards.For the template card example I suspect that the second card is a Mushroom bug. For the third card I have the same concern as above.
Steps to reproduce the issue
For the first picture the following YAML is used, varying
rows
as described above:For the second picture the following YAML is used, again, varying
rows
as described above:What version of Home Assistant Core has the issue?
2024.11.2
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Firefox 132 and Safari mobile latest
Which operating system are you using to run this browser?
macOS 15 and iOS mobile client
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: