Thank you for bringing this to our attention. We’ve decided to look into this issue further and may have found a solution that we’ll roll out with our upcoming update.
– – – – – The Technical – – – – –
In 1.1.9 we removed old styling brought over from the original Contact Form 7 break-off. It wasn’t accessible to users with disabilities and would prevent the form from being submitted if JavaScript was disabled instead of showing a reCaptcha-iframe fallback. We thought that the CSS absolute positioning of the iframe was causing A3 not to lazy-load the fall back iframe (v1.1.8). In any case A3 should not be lazy loading any items in noscript tags.
What we found is that the A3 plugin seems to disregard iframe with “content” inside of it.
<iframe></iframe>
will get lazy loaded but if we add a break in the iframe HTML
<iframe>
</iframe>
It seems to not even attempt to lazy load the iframe and Google doesn’t care for loading the fallback. Markup wise it’s not very different. We’re going to push this update in our next version which will also remove some jQuery dependencies ( using vanilla JavaScirpt as a replacement ). Hopefully that solves the A3 issues in the future.
– – – – –
Thanks again and have a wonderful rest of your week!