Skip to content
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

Spacing issue between row name and sub entities #176

Closed
SAOPP opened this issue Mar 3, 2021 · 8 comments
Closed

Spacing issue between row name and sub entities #176

SAOPP opened this issue Mar 3, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@SAOPP
Copy link

SAOPP commented Mar 3, 2021

Is it possible to automatically shift entities to the left closer to the main name if there are more than 3 of them?

For-example, I got it ova here:

image

If I add anotha sub-entity, in this example this is the lights, this card would be looks like this:

image

It can be fixed? Thanks.

@SAOPP
Copy link
Author

SAOPP commented Mar 3, 2021

And one more example, on the left there is a place to place the rssi sensor in one line, instead, as u can see in the screenshot, it is located on two lines, I would like such things to move closer to the left edge:

image

@bpetrikovics
Copy link

I second this. Maybe a padding option to allow us to reduce the unused area. I've noticed that rows with more than 3 entities are cut from the right unless my browser is running fullscreen, and also leaving off the right-most entities when I'm watching via mobile on the companion app (e.g. as if there were no further entities - no indication that information was cut).

@SAOPP
Copy link
Author

SAOPP commented Mar 9, 2021

Yes, in the mobile application, the rightmost objects go beyond the field of the card, which also causes discomfort.

@SAOPP
Copy link
Author

SAOPP commented Mar 9, 2021

Also anotha the same examples:

image

image

And mobile app issue:

image

@domoritz domoritz mentioned this issue Mar 22, 2021
@denilsonsa
Copy link

One more example…

I wanted to have four toggles in a single row (related to Adaptive Lighting component). lovelace-multiple-entity-row can do that, but the toggles get cropped to the right, so not all of them are visible. I also tried lovelace-paper-buttons-row, which manages to make all the buttons visible, but they are now ugly buttons instead of nice toggles.

Screenshot 1

Being able to remove the main name (and optionally also the icon) would be awesome for this case. Look:

Screenshot 2

That screenshot was made after adding display: none to the .info element inside <hui-generic-entity-row>, and then adding margin: auto to .entities-row to make the buttons centered (alternatively I could have used justify-content: space-between on the <hui-generic-entity-row> element, as that would keep the icon left-aligned while the buttons go right-aligned). I've done that on the browser developer tools, I don't have any code to share.

I can understand multiple-entity-row is reusing Home Assistant's hui-generic-entity-row, and that's great for most use-cases. But for some cases, it could be better to have more control over the layout.

@benct benct added the bug Something isn't working label Mar 23, 2021
@benct
Copy link
Owner

benct commented Mar 23, 2021

Should hopefully be fixed by home-assistant/frontend#8369.

Manual workaround with card-mod: .info { flex: 1 1 30%; }

@benct benct changed the title Move sub entities closer to the name of the main item Spacing issue between row name and sub entities Mar 23, 2021
@ivlis
Copy link

ivlis commented Apr 10, 2021

It has been broken since 2021.2 or 2021.1 AFAIR. This is annoying.

image

@benct benct closed this as completed Dec 17, 2021
@SAOPP
Copy link
Author

SAOPP commented Dec 26, 2022

Guys, I saw it again in lovelace, I remembered my problem, I decided to refresh my memory, as I understand it, now the problem still persists, right? And it is in the HA front?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants