[Security Solution][Windows: Firefox]List not showing until we go under full screen mode

[ghost]

Describe the bug
[Windows: Firefox]List not showing until we go under full screen mode

Build Details

Branch: Mains
Firefox : 100.0.2

Steps

• Login to Security App
• Have few alert generated on the kibana
• Attach alert to case
• Go to case details
• Click on Alert tab
• Observed that added alerts are not getting displayed until user go to full screen mode

Note: Issue is only on Firefox windows browser, on chrome windows this is working correctly

Screen-Cast

10.0.6.219.-.Remote.Desktop.Connection.2022-05-25.16-43-40.mp4

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[kqualters-elastic]

@karanbirsingh-qasource if you throttle the cpu in chrome by 6x, can you trigger the issue? If so, probably a duplicate of #129057

[ghost]

Hi @kqualters-elastic thanks for looking into the issue

Issue is not occuring on chrome browser as mentioned in bug also not occuring if we throttle the cpu in chrome by 6x.

• Chrome [ Issue not occuring ]

• Chrome with 6x throttle [ Issue not occuring ]

[cnasikas]

Hi @karanbirsingh-qasource! I could not reproduce the issue. Could you please test again on latest master?

[kqualters-elastic]

@cnasikas it's there for sure, and is a data grid bug I think. Other instances or possible related bugs #129057 #132901 https://github.com/elastic/sdh-security-team/issues/390

[ghost]

@cnasikas the issue is there on the mains branch as well .

sample.online-video-cutter.com.mp4

[cnasikas]

@kqualters-elastic @karanbirsingh-qasource Thank you both! Should we open an issue to EUI?

[kqualters-elastic]

Had a feeling this had a weird and not obvious root cause, @XavierM has reproduced it by setting a font size? #133691 (comment)

[cnasikas]

Should be fixed by #134268

[ghost]

HI @cnasikas

we have validated this issue on 8.3.0 BC5 and found this issue to be fixed ✔️ .

Build Details:

Version:8.3.0
BUILD: 53457
COMMIT: ba70bdf9fe5d28e832c40b7dbdade1e582133af1

Screen-shoot:

Hence we are closing this issue and adding "QA:Validated" to it.

thanks !!

[gabriellandau]

I've able to reliably reproduce this on my Windows 10 machine for months now. I can currently reproduce it in 8.4.0 BC1.

Chrome (currently 103.0.5060.134). Desktop resolution 1920x200. Display scaling is 100%. Page zoom is 100%.

There's two alerts here, but only one is visible in grid view:

The other one shows up in rendered view:

Restricting the time window so only one alert is within scope, we see zero alerts in the grid view:

It appears if I go full screen:

If you have a proposed fix but can't repro, I'd be happy to test it and send you screenshots, but I'm not set up to run a dev Kibana, so you'd have to host it.

[cnasikas]

Hi @gabriellandau,

Do you experience the same in the alerts table inside Cases? To see the alert table in a case please attach the alerts to a case. Then navigate to the case and press the alerts tab.

cc @XavierM

[gabriellandau]

@cnasikas it appears so. This is the case with one of the alerts attached.

That alert does show in full screen mode.

Here it is with both alerts attached. You can see a few pixels from the second entry:

I just noticed another potential bug. When you add an alert to a case which is already in that case, it creates an activity entry. This case only has two alerts, yet the activity log makes it appear as though 4 alerts are attached. I did take those actions, however, so "correct" behavior is not obvious.

[gabriellandau]

I did some testing yesterday with @kqualters-elastic over Slack. Enabling CPU and bandwidth throttling in Chrome's debug console did not prevent the grid view bug from manifesting.

[cnasikas]

Thanks for the detailed report! About

I just noticed another potential bug. When you add an alert to a case which is already in that case, it creates an activity entry. This case only has two alerts, yet the activity log makes it appear as though 4 alerts are attached. I did take those actions, however, so "correct" behavior is not obvious.

This is intentional. We add an activity entry for each user action regardless if the alert is already added. The alerts table shows only unique alerts. Maybe we should prevent attaching the same alert to a case in the future.

About the other bugs, I will delegate this to @XavierM. #134268 should have fixed it. We validated it at that point in time and it was working.