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
What is the bug?
In the 2.1.0 release of Opensearch Dashboards, we're planning to add a configurable option for either a condensed (single-line) or expanded (2-line) global header. However, this plugin currently hard-codes the header height into the popover positioning, which means the popover will no longer align with the menu link in the default mode:
How can one reproduce the bug?
Steps to reproduce the behavior:
Load opensearch dashboards with the dashboard-reports plugin and click on the Reporting menu link.
What is the expected behavior?
Because the plugin is responsible for rendering both the menu link and popover, it should use the correct EUI components, which will take care of positioning the popover relative to the menu link. Instead of building up large HTML strings with template literals, using EUI React components will make the UI controls much more maintainable and standardized.
The text was updated successfully, but these errors were encountered:
What is the bug?
In the
2.1.0
release of Opensearch Dashboards, we're planning to add a configurable option for either a condensed (single-line) or expanded (2-line) global header. However, this plugin currently hard-codes the header height into the popover positioning, which means the popover will no longer align with the menu link in the default mode:How can one reproduce the bug?
Steps to reproduce the behavior:
1
.What is the expected behavior?
Because the plugin is responsible for rendering both the menu link and popover, it should use the correct EUI components, which will take care of positioning the popover relative to the menu link. Instead of building up large HTML strings with template literals, using EUI React components will make the UI controls much more maintainable and standardized.
The text was updated successfully, but these errors were encountered: