#freetobook_unexpected

1 messages ¡ Page 1 of 1 (latest)

spiral sigilBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1250731764272336898

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

latent obsidian
#

Hi, let me help you with this.

#

There were no changes that I am aware of. Do you have a live website where I could reproduce the issue?

spiral sigilBOT
formal magnet
#

Unfortunately I have pushed a hotfix to workaround this issue (by also listening to the ready event), so I can't obviously reproduce it anymore. Either way, I am 95% sure this behaviour (the loaderstart event not consistently firing) is new

mint night
#

Hi
Are you using the latest Stripe Js ?

#

And is there a concrete way to reproduce the issue ?

formal magnet
#

I am using
"@stripe/stripe-js": "^2.2.0"
Here is the code I use to initialize the element:

  const paymentElement = elements.create(
    'payment',
    stripeElementsStore.generatePaymentElementOptions(),
  );

  if (!paymentElementContainer.value) {
    throw new Error(
      'Found no container to mount the Stripe payment element to',
    );
  }

  paymentElement.mount(paymentElementContainer.value);

  paymentElement.on('loaderstart', () => {
    status.value = StripePaymentStatus.Ready;
  });
};```

The `loaderstart` event there only seems to fire periodically.

You could try to recreate it by visiting https://booking-directly.com/widgets/XLHFJufULzAX9LrfjWNxQ1XfdUhoY98XgOfPTbrD71gPbk0ZqfqonrIL7yPJR/properties/40639/guest-details?search_stay_dates={%22checkInDate%22:%222024-06-15%22,%22checkOutDate%22:%222024-06-16%22}&search_occupancies=[{%22numberOfAdults%22:2,%22children%22:[]}]&booking_itinerary={%22checkInDate%22:%222024-06-15%22,%22checkOutDate%22:%222024-06-16%22,%22checkInTime%22:null,%22specialRequests%22:%22%22,%22unitItinerary%22:[{%22unitId%22:247614,%22offerId%22:%22N14360%22,%22occupancy%22:{%22numberOfAdults%22:2,%22children%22:[]},%22selectedMealTypes%22:[],%22leadGuestName%22:%22%22}],%22selectedExtraItinerary%22:[],%22mandatoryExtraItinerary%22:[]}, filling in some sample details, and then clicking 'continue'. 

It is on this page that the `loaderstart` event is not firing consistently.
mint night
#

You are not using the latest version

formal magnet
#

I can, but is there nothing else happening here? To reiterate, this has been working fine for months. We have changed nothing on our end. The issue has only been noticed this morning

mint night
#

Sorry, I can't tell much here... is there a clear way to reprodcue the issue? but in all cases, your using an old Stripe js version.

#

The issue has only been noticed this morning
So maybe some changes on your website is behind this behavior...

#

The recommendation here, is to first migrate to the latest stripe js (v3) and see if you still noticing the behavior. If so, please share a clear reprodcution steps.

formal magnet
#

Again, we have changed nothing on our end. I will try updating the version, but I see no reason why this would be relevant since everything has been working fine for months. Thanks for the help.