#blargz_iframe-elements-queryselector
candid impBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1268976948550303775
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
finite junco
I'm not sure if they do or not. That's kind of a big question unfortunately, as there are a lot of different elements
candid impBOT
torn owl
Interested only in payment and address elements
iron hazel
Hi 👋
My colleague had to go so I'm stepping in. I'm not sure what you are asking this for. We do not permit read state or directly manipulating the elements loaded within the Iframe for the Payment or Address Element.
torn owl
we have some custom tabindex logic that does a querySelector for all focusable elements, which is currently not searching for iframes. I need to expand our search to iframes from stripe. I'd like to rely on the name as the way of querying for them, and just wanted to verify if this approach is safe.
we are not interested in manipulating the elements directly
iron hazel
Unfortunately we do not guarantee this naming will remain consistent. As the _privateStripe.. nameing structure implies, this is private to Stripe and we can and do change things like this if it suits our needs.