choose entity drop down too narrow

ckuhtz commented 1 year ago

Checklist

[X] I have updated to the latest available Home Assistant version.
[X] I have cleared the cache of my browser.
[X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

Can't identify which entity is which when multiple are present (including as a search result).

Describe the behavior you expected

Being able to distinguish entities in the drop down

Steps to reproduce the issue

Select History on UI
Select Choose entity
Click on drop down menu for Choose entity
Start typing in text to pattern match an entity name ID or browse the list. In the example attached, I have multiple entities that have 'press' in their name and it's impossible to tell from the UI dropdown which is which as the name is truncated. The UI should support the identification of which entity is which when there are multiple in the dropdown (e.g., wider drop down, support scrolling horizontally in the dropdown, show the full entity ID and name when mousing over the items, etc).

What version of Home Assistant Core has the issue?

core-2022.12.8

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

Home Assistant 2022.12.8
Frontend 20221213.1 - latest

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

ildar170975 commented 1 year ago

Same https://github.com/home-assistant/frontend/issues/13671

karwosts commented 1 year ago

Linked pull request increase the entity selector width to 400px.

ildar170975 commented 1 year ago

Even after https://github.com/home-assistant/frontend/pull/14970 a list may be narrow:

This list may be wider:

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 year ago

up

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 year ago

Up

ckuhtz commented 1 year ago

This seems like such a simple issue..

github-actions[bot] commented 10 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 10 months ago

up

github-actions[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 7 months ago

up

github-actions[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ckuhtz commented 4 months ago

up

github-actions[bot] commented 1 month ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 month ago

up

home-assistant / frontend