#Ange
cold spindle
fossil bear
Hello 👋
Let's chat here
Can you check if the events are firing with an inline listener?
if (event.complete) {
// Extract potentially complete address
const address = event.value.address;
}
}} />```
fresh forge
Unfortunately that also did not work
fossil bear
huh interesting... do you see the address element on the page though?
fresh forge
Yes I do, I can type, the Element expands its fields as expected, etc
Here's a screenshot
fossil bear
If you comment out the element does the warning/error about cookie go away?
fresh forge
Added a button on the same page with an onClick listener does work, so I think it's specific to the stripe Element
let me check that
If I comment out all Stripe related things (including imports, the Element, loadStripe, etc) then yes the cookie error goes away
Presence of just one import from Stripe brings back the cookie error. These are the affected resources from the message:
fossil bear
huh okay.. Let me see if I can reproduce this behavior.
In the meantime, can you check if your code is identical to the example code or are there any differences?
fresh forge
The only difference I can see is that in step 3 of the guide which shows the example onChange handler (https://stripe.com/docs/elements/address-element/collect-addresses?platform=web&client=react#web-retrieve-address), I still have my mode set on the Element. But I think that's required since absence of the options param is actually an error
<AddressElement
options={{mode: 'shipping'}}
onChange={() => {console.log('inline listener')}}>
</AddressElement>```Checking the loadStripe setup logic now
I don't see any differences with my loadStripe logic. I also doubled checked my API_KEY (I am using a test mode API_key right now)
fossil bear
Gotcha, trying to reproduce..
fresh forge
ty
I did find this support article that is potentially about this issue, but it is talking about the resolution: https://support.stripe.com/questions/chrome-80-samesite-cookie-change.
Given the changes to prep for this Chrome change on Stripe side, it is unexpected that I see this as an error
fossil bear
okay yeah so I was able to reproduce this behavior on glitch
Let me build a local app and double check. I'll raise this internally and hopefully we can fix it soon.
In the meantime, would you mind writing into our support via
https://support.stripe.com/?contact=true about your issue and mention that you spoke with hanzo on discord? I'll grab the email and respond to you so that we can keep you updated about this
fresh forge
Sure, should I do the send-an-email option?
fossil bear
yes
fresh forge
Sure, will do that now
Is there any workaround, or do you suspect a bug ?
(sent the support email)
fossil bear
Most likely a bug, looking for the email. Just a sec
okay found the email. I will respond as soon as we have an update.
fresh forge
Ok thank you. So does this mean I cannot use StripeJS / Elements for now?
(btw I have a Checkout client/server integration and it's working fine in case that data point helps)
fossil bear
Yeah don't think there's an alternative at the moment
fossil bear
👍 Appreciate your patience!