Issues with reCAPTCHA v2 inside a modal in Internet Explorer 8 and up

I use reCAPTCHA v2 on a website using the grecaptcha.render function.

I have tested it in Firefox and Chrome without any issues.

In Internet Explorer 8 - 11 it won’t work. I’ve tested it on multiple computers and different networks.

It won’t allow a correct entry of the captcha nor will it allow for it’s submission when inside a Bootstrap Modal.

YouTube video to display the issue: https://youtu.be/KnaQqqaz-00

JSFiddle to demonstrate the issue: http://fiddle.jshell.net/emilhem/Lgovn28f/4/

Does anyone else experience this issue? Is there a solution to the issue I’m experiencing?

[marcvangend]

I am honestly amazed that this is how Bootstrap treats a contributor to the project. Here is someone who has spent time and effort to provide a useful, constructive bug report, only to be smacked in the face, first by a bot, then by a wont-fix from a maintainer who didn’t investigate the cause of the problem.

It may or may not be a coincidence, but on the exact same day that this issue was opened and closed, a 2 months old question on StackOverflow received an answer containing a workaround which looks like this:

$.fn.modal.Constructor.prototype.enforceFocus = function () { };

In other words, the problem is in a function coming from Bootstrap itself. It probably serves a purpose, but breaks other scripts by stealing focus. Especially since this “other script” is not some hackish piece of custom JS, but Google’s Recaptcha, I kindly ask you to reconsider your decision and offer @emilhem your apologies.

[bardiharborow]

Bootstrap receives a large quantity of low quality bug reports where the user is at fault rather than Bootstrap. This may not be the case with your bug report, but we can’t always determine this at first glance and due to the number of issues we deal with we often default to closing. Getting angry at the core team (who are just volunteers doing their best), is not helpful.

@marcvangend seems to have demonstrated that it’s a problem on our end, so I’ve added this issue to my review list. I can’t however make any guarantees about backporting a fix as support for v3 has mostly ceased.