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

Y axis labels are cut off in the history card preview #24027

Closed
3 of 4 tasks
RubenKelevra opened this issue Feb 2, 2025 · 0 comments · Fixed by #24040
Closed
3 of 4 tasks

Y axis labels are cut off in the history card preview #24027

RubenKelevra opened this issue Feb 2, 2025 · 0 comments · Fixed by #24040
Assignees

Comments

@RubenKelevra
Copy link

Checklist

  • 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

I've noticed that in the preview of the history card the Y axis labels are cut off:

Preview:

Image

Rendering after saving:

Image

Describe the behavior you expected

Preview and final rendering should look the same

Steps to reproduce the issue

  1. Add history card
  2. add element which can be plotted as graph
  3. see cut off Y axis labeling

What version of Home Assistant Core has the issue?

core-2025.2.0b6

What was the last working version of Home Assistant Core?

core-2025.1.0

In which browser are you experiencing the issue?

Android App 2025.1.6-full / Chrome 128.0.6613.189

Which operating system are you using to run this browser?

Android 12 / Arch Linux

State of relevant entities

Problem-relevant frontend configuration

Javascript errors shown in your browser console/inspector

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants