#tfh-3ds-modalconflict
1 messages ยท Page 1 of 1 (latest)
tfh-3ds-modalconflict
@lavish minnow Hello! I don't think it makes sense for you to switch to that approach. It's extremely complex to build right and highly discouraged.
I don't fully grasp what you are describing but you need to make sure you don't have any modal/overlay/UI that conflicts with our own modal
That's fair. The trouble is, it seems, the Stripe iframe gets injected at the beginning of the body tag and our modal is at the end, so even though the z-index of the iframe is extremely large and it appears over our modal, our backdrop seems to still obscure it. Is there any way to control where in the document the iframe is injected/rendered?
No you have no control over this. You should hide your backdrop/overlay/modal before calling confirmPayment() and then show it after it's done
I see
I shall see what I can do. Thank you, though. You did confirm what I suspected and that was the complexity of taking control of the iframe rendering. It felt like the wrong approach but I was hoping there was some alternative I hadn't known of or considered
yeah this is definitely tough. We also see devs that have third-party libraries that "steal" the keyboard focus
it's so hard to debug all of this ๐ฆ
Yeah no doubt. Well I appreciate your help, regardless ๐
happy to help!
Hey there, I actually had a small update. I've found that if I add this one CSS property to the div Stripe creates for the 3D Secure iframe, it works!
pointer-events: all;
Hello! I'm taking over and catching up...
Thank you kindly ๐
I'm wondering if there is any realistic way I could modify this in code?
I doubt it. Do you have this page online where I can look at it? Really difficult to debug this kind of thing without being able to inspect it.
Of course. Unfortunately I do not. But I will try to get something for you. Will need 20-30 mins or so
I'll put it out there that adding that property to the div that's created might not be a bad addition to the Stripe SDK, regardless
Yeah, I can flag that internally. Kinda surprised it's not already there, but there might be a good reason we don't have it.
Fair enough
How's it going?