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

Manage Graphs Button Unclickable Due to Excessive Graphs List #482

Closed
Naseem77 opened this issue Sep 24, 2024 · 0 comments · Fixed by #497
Closed

Manage Graphs Button Unclickable Due to Excessive Graphs List #482

Naseem77 opened this issue Sep 24, 2024 · 0 comments · Fixed by #497
Assignees
Labels
enhancement New feature or request

Comments

@Naseem77
Copy link
Contributor

Description: When a large number of graphs are created, the "Manage Graphs" button in the UI becomes inaccessible. The list of graphs grows too long and pushes the "Manage Graphs" button out of view, making it impossible to interact with the button.

Steps to Reproduce:

Navigate to the graph URL
Create a large number of graphs (more than the UI can display at once).
Scroll down to locate the "Manage Graphs" button.

Expected Behavior: The "Manage Graphs" button should always be visible, or a scrolling option should be available to navigate through the list of graphs.

Actual Behavior: The "Manage Graphs" button is pushed off-screen and cannot be accessed, making it impossible to manage or configure graphs.

Suggested Fix: Add a scrolling option for the list of graphs to ensure that users can scroll through all graphs and access the "Manage Graphs" button even when the list is long.

Image

@Naseem77 Naseem77 added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Sep 24, 2024
@Anchel123 Anchel123 linked a pull request Sep 26, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants