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

Long message text goes outside of persistent_notification card width #3160

Closed
SeanPM5 opened this issue May 5, 2019 · 0 comments · Fixed by #3557
Closed

Long message text goes outside of persistent_notification card width #3160

SeanPM5 opened this issue May 5, 2019 · 0 comments · Fixed by #3557
Assignees
Projects

Comments

@SeanPM5
Copy link
Contributor

SeanPM5 commented May 5, 2019

Home Assistant release with the issue:
0.92.2

UI (States or Lovelace UI?):
Lovelace

Description of problem:
I have an automation that notifies me via persistent_notification of new devices tracked. The iOS 2.0 beta app is currently using a long UDID for the device_tracker until backend changes are merged in 0.93 I guess. So the message is:

New Device Tracked: None (device_tracker.7b50aa345032439dacb17b31c3c08acb)

But this goes outside of the card width instead of wrapping to a second line.

IMG_9943

Furthermore, you cannot seem to select this text and copy contents of a persistent_notification which seems like a super weird thing to restrict.

I had to open the Chrome inspector just to be able to copy the device_tracker entity id here, and most regular users are not going to know how to do that.

Possibly related to this issue with Home Assistant Cloud settings I reported a while back #2982. I am guessing it's a problem with all the cards then?

@iantrich iantrich added this to To do in Frontend via automation Aug 31, 2019
@iantrich iantrich moved this from To do to In progress in Frontend Aug 31, 2019
@iantrich iantrich self-assigned this Sep 1, 2019
Frontend automation moved this from In progress to Done Sep 2, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Jul 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Frontend
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants