Hi @iandrew
Looks like this is a small usecase that didn’t come to mind for us when we were working out some bugfixes in 1.4.2. Specifically the use of reCAPTCHA on other forms shown on the same page.
Part of the 1.4.2 release is detecting if Google reCAPTCHA is on the page, and if it is, disabling our submit button. However, we were intending for it to also be attached to our form, not a different form elsewhere. Once a visitor to the page validated themselves, the button would be enabled. The issue that was aiming to be solved was that you could still submit to the form without validating yourself, if the form had a custom redirect. We were also hoping it’d help prevent some extra spam that was getting through that we didn’t realize previously
Here’s where the spinning button detail comes in. If our settings had the reCAPTCHA api keys saved to them, then it would append a “has-recaptcha” to the form, and the disabled button would be normal instead of some custom graphic we added previously to help indicate activity. We wager you don’t have your keys saved there at the moment because of the use of reCAPTCHA in other forms, thus it’s getting a “no-repcatcha” class and not getting the normal disabled button behavior we intended. An unexpected rock and a hard place that I mentioned not anticipating at the start here.
We don’t have an immediate solution to remedy this, but we have some quick leads that we’d love to explore to help address this potential situation. We’ll get back to you as soon as we can.
