-
Notifications
You must be signed in to change notification settings - Fork 186
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
Wrong behavior from the Flyout component in Wazuh Dashboard 2.x #4597
Comments
Issue researchFiles involved
We use a customized flyout component called WzFlyout. |
The These 2 functionalities are now provided out-of-the-box by the |
Sections involvedModules
Security
Management
|
Investigating why it is having this behavior when modifying some field in the flyout and clicking outside the flyout to close it without asking, I noticed that the EuiFlyout component, in the version of elastic EUI that was forked by the OpenSearch Dashboard guys (elastic EUI v34.6.0), It has some bugs that are fixed in a higher version of Elastic EUI (v36.x).
I am analyzing different alternatives to solve this problem we are having, and if we put the properties of |
The problem does not come from the EuiFlyout component, the problem comes from the EuiOverlayMask component with the click event, it is solved in this PR of Elastic EUI that goes to version 36.0.0.0.0 and OpenSearch dashboard made the fork of a previous version (34.6.0) and they did not solve it yet. |
Description
A new problem has been found in every version of OpenSearch 2.x, more concretely related to the OpenSearch Dashboards.
We use the flyout component from EUI, which closes automatically when the user clicks outside it. However, in 2.x, these components will also close automatically when clicking inside them. This is not the correct behavior, and it's probably related to OSD updating the EUI library to a newer version, breaking our customized components behavior.
Video
flyoutclose.mp4
We'll need to hunt and fix this bug.
Affected views
Modules
Security
Management
Related release notes
Originally posted by @yenienserrano in #4160 (comment)
The text was updated successfully, but these errors were encountered: