".closest('form').prop('id')" problematic if form has an 'id' element
If a customization, extension, configuration, etc introduces an input with the name or id "id", the .prop() will incorrectly grab that element instead of the form and have a bad ID, breaking Stripe processing. For example we have a shim extension to add a hidden "id" element to alleviate certain session issues that have been cropping up lately by passing event ID from register to confirm, and if someone picked "id" as their honeypot field it would also break Stripe.
This situation doesn't appear in CiviCRM Core, but it could in the future.
Considering the console in the attached example, I believe .attr() will work here instead. Do you see issues with that approach?
Potential MR if this makes sense and your testing also doesn't reveal other issues: !28 (merged)