[EuiInMemoryTable] inside an [EuiModal] covers it with a red layer

[lior-fortifieddata]

https://codesandbox.io/s/sharp-meninsky-v7x6pt?file=/demo.js

see gif

it's coming from here

[elizabetdev]

Hi @lior-fortifieddata.

Thanks for reporting.

This issue is going to be fixed on #6321.

[lior-fortifieddata]

Thanks for the quick fix.

…

________________________________ From: Elizabet Oliveira ***@***.***> Sent: Thursday, October 27, 2022 4:43:14 PM To: elastic/eui ***@***.***> Cc: Lior Goldemberg ***@***.***>; Mention ***@***.***> Subject: Re: [elastic/eui] [EuiInMemoryTable] inside an [EuiModal] covers it with a red layer (Issue #6328) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi @lior-fortifieddata<https://github.com/lior-fortifieddata>. Thanks for reporting. This issue is going to be fixed on #6321<#6321>. — Reply to this email directly, view it on GitHub<#6328 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOIHQW6LDRNDS4Q5KJ4QP3LWFKBHFANCNFSM6AAAAAARPZZFWY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[lior-fortifieddata]

@breehall @constancecchen @miukimiu
The bug is not fixed on 70.1.0, even though the commit of the related issue is merged. should it?

[cee-chen]

The commit being merged into main does not mean it has been released - this bugfix is not yet in our regular weekly release cadence. We have instead backported it to 67.x for our latest Kibana upgrade PR to ensure it reaches Kibana by 8.6 FF.

[lior-fortifieddata]

Thanks for replying. Is there a way to identify when an issue is deployed? Tag/ other way? From: Constance ***@***.***> Sent: Monday, 7 November 2022 17:37 To: elastic/eui ***@***.***> Cc: Lior Goldemberg ***@***.***>; Mention ***@***.***> Subject: Re: [elastic/eui] [EuiInMemoryTable] inside an [EuiModal] covers it with a red layer (Issue #6328) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. The commit being merged into main does not mean it has been released - this bugfix is not yet in our regular weekly release cadence. We have instead backported 67.x for our latest Kibana upgrade PR to ensure it reaches Kibana by 8.6 FF. — Reply to this email directly, view it on GitHub<#6328 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOIHQW5HHY6U2UB2OMLGG3DWHEO3PANCNFSM6AAAAAARPZZFWY>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[cee-chen]

We usually do a release every Tuesday, so things get in relatively quickly once merged into main. You can subscribe to our repo releases to see a changelog of all commits in that release.

This fix in particular should now be in our latest 70.2.0 release.