You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The uptime card styling is currently broken, and the graph does not fit into the container.
How to reproduce the bug
Following the install instructions (a fresh OhDear Pulse install, add the cards to the dashboard, add the config, etc) - we see the graph spilling outside the card container.
Package Version
1.1.0
PHP Version
8.3.12
Laravel Version
10.48.10
Which operating systems does with happen with?
macOS, Linux
Notes
Adding a relative class to the pulse card component seems to fix the issue. What's strange it that this problem only recently started happening (3 days ago was when my manager reported it) -- My first install of the component was in September, and it looked fine:
Additional versioning and site data
Laravel Version ...................................... 10.48.10
PHP Version ............................................ 8.3.12
Composer Version ........................................ 2.7.7
Environment ............................................. local
Pulse ....................................................
Enabled ............................................... ENABLED
Version ................................................ v1.2.3
Livewire ...............................................
Livewire ............................................... v3.5.0
The text was updated successfully, but these errors were encountered:
What happened?
The uptime card styling is currently broken, and the graph does not fit into the container.
How to reproduce the bug
Following the install instructions (a fresh OhDear Pulse install, add the cards to the dashboard, add the config, etc) - we see the graph spilling outside the card container.
Package Version
1.1.0
PHP Version
8.3.12
Laravel Version
10.48.10
Which operating systems does with happen with?
macOS, Linux
Notes
Adding a
relative
class to the pulse card component seems to fix the issue. What's strange it that this problem only recently started happening (3 days ago was when my manager reported it) -- My first install of the component was in September, and it looked fine:Additional versioning and site data
The text was updated successfully, but these errors were encountered: