-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Sections: unable to place more than 1 cards next to 3x3 card. #22846
Comments
Hi @AJediIAm, |
Hi @wendevlin, After a bit of fiddling, I realized the picture element card had a layout of 1 high and 3 wide while it showed the picture at its full height (which is closer to 4 high). So, the actual bug is the initial height of the picture element. |
Hi 👋 Yeah all cards are not migrated yet to support the grid system. As a workaround, you have to set the size manually for now. |
Ok, so it's a known issue. |
We can close it, this issue will be fixed when we will redesign and adapt the card to the grid section. There is no need to keep it open. Thank you for the report. |
Checklist
Describe the issue you are experiencing
I'm trying to create a section with a 3x3 card next to 3 1x1 cards. After placing the first 1x1 card, the option to place additional cards disappears.
Update: the picture element turned out to be a 3x1 card while showing as a 3x3 or 3x4 card. This is why only 1 card could be placed next to it.
Describe the behavior you expected
I would expect to be able to place 3 1x1 cards next to the 3x3 card.
Update:
I would expect a picture element to have a height of at least the height of the picture.
Steps to reproduce the issue
...
Update:
What version of Home Assistant Core has the issue?
20241106.2
What was the last working version of Home Assistant Core?
2024.11.2
In which browser are you experiencing the issue with?
Chrome 131.0.6778.39
Which operating system are you using to run this browser?
Android
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: