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
After installing the argocd-extension-metrics extension, the UI elements specifically in the sidebar menu are misaligned. The collapsible menu headers (e.g., LABELS, PROJECTS, CLUSTERS, NAMESPACES) are no longer aligned with their respective toggle icons.
To Reproduce:
Install argocd-extension-metrics on Argo CD version v2.10.4.
Access the Argo CD UI and observe the sidebar menu.
Expected behavior:
The menu headers and toggle icons should be aligned properly, similar to how they are displayed without the argocd-extension-metrics extension.
Screenshots:
Attached is a screenshot demonstrating the UI misalignment in the sidebar menu.
Additional context:
This issue seems to be a direct result of installing the argocd-extension-metrics extension and affects the overall usability of the UI.
Would appreciate any guidance on how to fix this or information on a potential upcoming patch that addresses this issue.
The text was updated successfully, but these errors were encountered:
Version:
Argo CD v2.10.4
argocd-extension-metrics v1.0.0
Describe the bug:
After installing the
argocd-extension-metrics
extension, the UI elements specifically in the sidebar menu are misaligned. The collapsible menu headers (e.g., LABELS, PROJECTS, CLUSTERS, NAMESPACES) are no longer aligned with their respective toggle icons.To Reproduce:
argocd-extension-metrics
on Argo CD version v2.10.4.Expected behavior:
The menu headers and toggle icons should be aligned properly, similar to how they are displayed without the
argocd-extension-metrics
extension.Screenshots:
Attached is a screenshot demonstrating the UI misalignment in the sidebar menu.
Additional context:
This issue seems to be a direct result of installing the
argocd-extension-metrics
extension and affects the overall usability of the UI.Would appreciate any guidance on how to fix this or information on a potential upcoming patch that addresses this issue.
The text was updated successfully, but these errors were encountered: