[Logs UI] Log rate anomaly table breaks the layout on IE11

[weltenwort]

Problem description

Rendering the anomaly table in on the log rate analysis page pushes the right side of the page outside the frame:

Commenting out the table rendering causes the effect to disappear.

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[Zacqary]

Been pairing with @snide on this because I'm personally stumped. Some combination of display: table and width: 100% is causing the table element to expand to 20000-something pixels wide. Setting it to display: block instead causes each table cell to only be as wide as their widest content, not as wide as the surrounding panel.

It may be as simple as setting a max-width on the table, but it's not immediately clear what exactly that max should be considering it's a responsive layout. Also I don't know where the table is getting the 20k-wide display context from.

[snide]

So I've tried to get this page to reliably load in VM/IE11 and I just can't get it consistently to load and have inspector up at the same time. The logs UI in general has a lot of issues in IE and between the auto refreshing and the inability to load inspector I'm blocked from trying to resolve this.

Likely a problem with the nesting flex groups. This feels like a smaller problem for this application in whole as far as ie11 though as I'm getting 15 second loads on the actual log viewer itself.

[Zacqary]

The furthest along I was able to get was passing in a max-width: 80vw to the EuiBasicTable element if Javascript detected the user was running IE11.

However this doesn't fully fix the issue, because the surrounding EuiPanel was still stretched to a minimum of something like 1500px and I didn't know why.

I can try to reproduce to get a screenshot, but I've been running into the same stability issues with IE11 and VMs so that's easier said than done.

[Zacqary]

So I opened a draft PR with that JS IE-detection fix just so we have something. I don't know if we even want to consider merging something like that, but here it is. #49980

Difficulties with testing and debugging are making it hard to figure out much of anything else.