You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! We spotted an issue w/ the Stripe Element's form controls + FF + 1password. It seems that including both the PaymentElement and AddressElement on the same screen causes 1password to jump focus between both iframes repeatedly as they compete w/ each other.
I tried looking through the docs to see if there's a way to use a single iframe for both payment and address forms, but it seems there's not.
I know this is likely 1p more so than Stripe, but hoping that you've got a recommendation that we can apply here.
Environment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered:
Yes, it seems to impact Arc as well. No issues w/ Chrome/Safari that we can tell.
Continuously, sometimes just once or twice, sometimes repeatedly.
I've opened a support ticket w/ 1p as well. Just hoping you can provide a work around that doesn't involve moving address collection to a separate step.
@gdborton Thanks! Could you try one random thing and move the AddressElement to before the PaymentElement in the DOM? We have another recent issue that has a little bit of overlap with this: #567
What happened?
Hello! We spotted an issue w/ the Stripe Element's form controls + FF + 1password. It seems that including both the PaymentElement and AddressElement on the same screen causes 1password to jump focus between both iframes repeatedly as they compete w/ each other.
I tried looking through the docs to see if there's a way to use a single iframe for both payment and address forms, but it seems there's not.
I know this is likely 1p more so than Stripe, but hoping that you've got a recommendation that we can apply here.
Environment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered: