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.

Sign up for GitHub

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

Jump to bottom

partition metric errors with different widths #2249

Closed
Artessan opened this issue Dec 27, 2019 · 2 comments
Closed

partition metric errors with different widths #2249

Artessan opened this issue Dec 27, 2019 · 2 comments
Labels
bug Verified bug by the Nova team
Milestone
3.x

Comments

@Artessan
Copy link

Artessan commented Dec 27, 2019 •
edited
Loading

  • Laravel Version: 6.9.0
  • Nova Version: 2.9.2
  • PHP Version: 7.4
  • Database Driver & Version: pgsql 11
  • Operating System and Version: windows 10
  • Browser type and version: edge chromiun beta

Description:

  • when a partition metric card with one item in count and full width is rendered the chart overflow the card body.
    Captura de pantalla (56)

  • if the text of the metric item is to long the chart is over the content. (screen >= 1920 X 1080 )
    Captura de pantalla (57)

Steps To Reproduce:
@davidhemphill davidhemphill added the bug Verified bug by the Nova team label Feb 7, 2020
@mvdnbrk
Copy link

mvdnbrk commented Feb 7, 2020

Related to #1698

@jbrooksuk jbrooksuk added this to the v3.x milestone Apr 8, 2020
@jbrooksuk jbrooksuk removed the pending label Jul 27, 2020
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Verified bug by the Nova team
Projects
None yet
Milestone
3.x
Development

No branches or pull requests
4 participants
@davidhemphill @jbrooksuk @mvdnbrk @Artessan