hendrik t

Need this as well. Is this project still maintained @ctrlplusb ? might work on an implementation of this anyway in near future causeI need it for a project

Thanks for your reply. I will do some research on it. Regarding performance I think it can cause a second render-cycle. It needs to be ensured that it does not...

Okay, I see. Never thought about potential SSR problems so far. I was able to fix it for my usecase by only injecting enforceFocus = true into my last launched...

 Legit question but sadly no easy answer, we had lots of discussion about Modals vs No Modals, only one Modal at a time... But there are always exceptions....

I guess there is some sort of Race-condition in the ModalManager caused by a too late registration of the Second Modal! I tried to describe it in the Issue itself...

Yeah sorry for the misleading bug description but that was what I wanted to describe with "the first Modal claims it back". I should have written how it claims it...

Sorry my bad again. I wasn't aware of the fact that adding a Modal already triggers the DOM manipulations. Well, I guess without a refactor of the ModalManager it is...

 I think I am having the same issue like @rishadjb described above.