Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
emilhem opened this issue Mar 10, 2015 · 7 comments
Closed

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

emilhem opened this issue Mar 10, 2015 · 7 comments

Comments

@emilhem
Copy link

emilhem commented Mar 10, 2015

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?

@twbs-lmvtfy
Copy link

Hi @emilhem!

You appear to have posted a live example (https://fiddle.jshell.net/emilhem/Lgovn28f/2/show/light/), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

  • line 15, column 98: & did not start a character reference. (& probably should have been escaped as &.)

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!

(Please note that this is a fully automated comment.)

@emilhem
Copy link
Author

emilhem commented Mar 10, 2015

Fixed JSFiddle: http://fiddle.jshell.net/emilhem/Lgovn28f/4/

Extremely picky HTML5 validator...

@cvrebert
Copy link
Collaborator

Sorry, but we are unable to provide assistance for issues involving third-party widgets/libraries, such as reCAPTCHA. See also http://getbootstrap.com/javascript/#callout-third-party-libs
Please try asking on StackOverflow (or similar) instead. Thanks!

@cvrebert
Copy link
Collaborator

Although your use of setTimeout instead of .on('shown.bs.modal', ...) can't be helping things.

@marcvangend
Copy link

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.

@ghost
Copy link

ghost commented Nov 16, 2016

How is this still closed?

It's been kindly pointed out already that the problem is with a function that by all means seems to be headed towards the deprecated pile in v4.

Any chance of fixing the bug and supporting those still using the official release version and not yet on the alpha train?

@bardiharborow
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants