Some in these recaptcha threads thought it was due to the Firefox 125.0.3 update when it was released on April 29, while this recent recaptcha issue only occurred in the last day at most as per posts here. So this helps rule the Fx 125.0.3 update out.

Workaround Until this is Fixed. By the way, this is a Google issue not really a Firefox issue. 1. In the address bar, type: about:config 2. Search for: general.useragent.override 3. Select "String" and then the + button 4. Copy and Paste this into the field: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) AppleWebKit Gecko/20100101 Firefox/125.0 5. Click the Checkmark Blue button. You're done. 6. Now Bookmark this setting so you can delete it when this issue is fixed. Don't forget

should it read

general.useragent.override Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) AppleWebKit Gecko/20100101 Firefox/125.0

or does it replace the general/useragent.override ?

i assume it has to be set to true? and which of Boolean/Number/String ? also i dont see any Checkmark Blue button

Hello, I have the same exact problem. Since yesterday, when I click on the recaptcha, it just keeps circling. The page just works fine with other browsers. Tried everything (including cleaning the registry keys, preferences, tracking, etc.,) And on 2 pc's , Windows 11 et windows 10 with firefox 125.0.3, the day before, everything was oj

I've got this problem also since 125.0.2, after update to 125.0.3 the captcha worked. But since today there is the spinning circle of death, no captcha is shown... But: Now it works again! What I have changed is following setting (FF, Security...): Allow pop-up for "http://google.com" and "https://google.com"

I hope this works for a lot of you with the same behavior...

Greatings Nixvista

If you can't figure out the about:config workaround, install User-Agent Switcher and change the OS from "Windows" to "Linux" until Google fixes the issue.

I just tried to log into a site that requires a captcha verification. When I clicked the box a check mark appeared and I was able to log in. WOOHOO This just proves what people were saying that it was a Google problem and not a FF problem. Thanks to everyone who suggested work arounds. The world is right again. HAHAHA

I believe Google want to force some another user to give up on FF, so a lot ones will just start use chrome because of that, in that middle time Google fix that..., I believe its enough to be in a court!

Anyway, to solve that just do it:

open FF, type: about:config type general.useragent.override and create a new one with this code: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.6422.14 Safari/537.36

after that be fixed by Google, just delete that record: general.useragent.override

DONT install that addons, because all of that ask for your DATA, and that will be a problem if you have sensitive professional data.

Regards

I don't think simply blaming Google and leaving it up to them to make changes is helpful when no other browsers are affected. The logical conclusion is that beta testing for the last Foxfire release didn't include compatibility with recaptcha.

I don't think simply blaming Google and leaving it up to them to make changes is helpful when no other browsers are affected. The logical conclusion is that beta testing for the last Foxfire release didn't include compatibility with recaptcha.

I understand why you think that, but here's why that logic doesn't work in this case.

(1) Rolling back to Firefox 125.0.2 or any other version of Firefox did not solve the problem.

(2) You could make reCAPTCHA work without any code changes in Firefox simply by having your Firefox/Windows identify itself to Google as Firefox/Mac. Note that the user agent string has not changed since Firefox 125.0.1 since that last decimal part isn't included.

(3) The bug was identified as a script coding error in reCAPTCHA by a contributor to the bug report:

The culprit is a dark-mode detection logic for Firefox Windows:

 ($N && jT
  ? ((b = QP(p)),
    (b.style.backgroundColor = "rgb(255, 255, 255)"),
    oB(b),
    (c = z[44](26, b, "backgroundColor")),
    xx(b),
    (Q = "rgb(255, 255, 255)" !== c))
  : (Q = D)),

which reads:

 (isFirefox && isWindows
  ? ((b = document.createElement("div")),
    (b.style.backgroundColor = "rgb(255, 255, 255)"),
    document.body.appendChild(b),
    (c =window.getComputedStyle(b).getPropertyValue("backgroundColor")),
    document.body.removeChild(b),
    (Q = "rgb(255, 255, 255)" !== c))
  : (Q = D)),

However, since the script is in the head, `document.body` is not available. I cannot think of easy way of shimming this on the Firefox side.

As you can see, Google added specific logic for Firefox/Windows that doesn't execute in any other browser, and that is where it fails.

Was it malicious? I doubt it, but I think this indicates that no one at the relevant part of Google bothered testing in Firefox. If true, that's very sad.

From this closed bug it looks that Google has fixed this issue, so you can test this by disabling the extension.

• https://bugzilla.mozilla.org/show_bug.cgi?id=1894735#c23