Bruno Dias

@phayman actually this is currect. If you have something that has no width or height, it will be considered a "non-tababble element". If seem that you ReactModalPortal element (the one...

Unfortunately, this is not an easy fix. There are other threads where I explain that this behavior comes from `react 16.3+`, where they changed how the lifecycle works, mostly for...

@atomanyih Are your tests running in concurrently?

@ADTC Working with a single modal is pretty easy. Once you start stacking and/or nesting modals + react new lifecycle the problems gets really big. It's impossible to know all...

@giacomoalonzi This is the expected behavior. Each modal you instantiate will create a node element where the modal will be placed when it opens up. It's still open a feature...

@neilhsmith A good place to start is to update the available examples using the correct accessibility functionality. Other examples would be really nice, specially combining libraries like styled components and...

Great. Let me know if you need anything.

@tonypee and would be lovely if someone made the fix, right?

@MadhavKauntia which version are you using?

Please, check if this is an incompatibility with newer version of react like 17+.