Column shake in EuiDataGrid in the security alert view

[aarju]

Describe the bug After adding a column to the view in the security alert table if the column was set to a certain width it causes the table to constantly jump around displaying the scroll bars then not displaying them. See the below video for the bug in action. Resizing the column or the browser window stops the activity.

https://github.com/elastic/eui/assets/14032876/fe39110f-08c2-4ed2-b666-4f580c076543

Environment and versions

• EUI version:
• React version:
• Kibana version (if applicable): 8.9.0
• Browser: Chrome 115
• Operating System: Windows

To Reproduce I'm not really sure how to reproduce this. When adding a column it depends on the length of the values within the field in relation to the size of the browser window. When I tried to open the developer tools it changes the width of the browser display and causes the bug to stop.

Expected behavior The screen shouldn't shake

Additional context This is part of the Elastic Infosec team's SIEM cluster.

[1Copenut]

Thank you for the bug report @aarju. I'll reach out privately for a cloud URL to test.

[cee-chen]

@aarju can you confirm if this is happening in Kibana main or just 8.9? Kevin Qualters recently contributed an EuiDataGrid fix that should stabilize height/width recalculations (https://github.com/elastic/eui/pull/6895). This fix is not in 8.9 but will be in 8.10, and we could potentially backport it to 8.9 if it does indeed fix the issue

[aarju]

This is in 8.9

[cee-chen]

Just wanted to recap the conversation we had in Slack:

Unfortunately we need the issue to be reproducible in EUI (either in a CodeSandbox or on our production docs site) to materially help figure out a fix. Our team is small, and we don't have the resources to chase down bugs that are both specific to a consumer's usage of a component and hard to reproduce.

That being said we also always welcome contributions to EUI, so if y'all manage to track this down on your own, please do send a PR our way! (or again, another option is waiting to see if 8.10 fixes the issue)

I'll leave this issue open for now in case @kqualters-elastic or another Elastic dev is able to work on this more/wants to pick this up, but EUI will not be able to work on this issue ourselves in its current state and this issue will auto-close in a year if no other activity is reported.

[github-actions[bot]]

👋 Thank you for your suggestion or request! While the EUI team agrees that it's valid, it's unlikely that we will prioritize this issue on our roadmap. We'll leave the issue open if you or anyone else in the community wants to implement it by contributing to EUI. If not, this issue will auto close in one year.

Log | Bot Usage

[github-actions[bot]]

👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.