+++ This bug was initially created as a clone of Bug #1530784 +++

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

I go to a site, fill in the information required and click 'submit' I get a response stating I have to do the "Captcha" but firefox never has a Captcha that I can click on so I have to ALWAYS go to Google Chrome, re-fill in the information and click on THEIR captcha. Where's Firefox's Captcha and why is it missing?

Actual results:

I go to a site, fill in the information required and click 'submit' I get a response stating I have to do the "Captcha" but firefox never has a Captcha that I can click on so I have to ALWAYS go to Google Chrome, re-fill in the information and click on THEIR captcha.

Expected results:

Firefox SHOULD have a captcha when it is required by some sites. Since Google Chrome has no problem with showing a captcha why does not firefox?

======
I am constantly experiencing this bug, being unable to access sites like: hobbyking, patientaccess, mail.com, royalmail, dpd, prusa3d with firefox AT ALL. In many cases I am unaware captcha is being requested just that registration or login has failed. So I am FORCED to use Chrome [spit] to access these sites some of which are necessary for my health.
Firefox Quantum 68.6.0esr (64-bit)
Linux version 4.19.0-6-amd64 ([email protected]) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
NO Plugins
NO Add-ons
NO Extensions
NO Themes

Have you tried safe mode? Or a fresh profile? Perhaps an add-on is interfering. You're using Firefox 65? That's really old, try downloading current Firefox and see if you still have the issue. AFAIK we haven't been seeing complaints like this so I first suspect something about your specific setup.

As stated in my earlier report; I use stock Debian Buster and the standard Firefox version installed is Firefox Quantum 68.6.0esr NOT 65 as you state. Not trying to be difficult, but if you had taken the trouble to read my report you would know this, and also the information you asked regarding Add-ons.

I use Debian because I want the stability and security so, no, I am sorry I will not be downloading the 'latest' version as my version IS the LATEST 'esr' version and as the 'Extended Support Release' is supposed to be supported for an extended period I would expect bug fixes to be backported to this code base.

Regards
F

Please have a look at https://bugzilla.mozilla.org/page.cgi?id=etiquette.html before you comment again, thanks.

The reason I said 65 is because in the first comment it says "User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0"

Have you tried safe mode? Or a fresh profile? Safe mode and a fresh profile changes more things than just addons.

Bug fixes are not backported to esr, only security bugs and some very bad bugs. You can download the latest version and just uncompress it into a temp directory without installing it over top your current version in order to test it and use a separate profile from your main profile. This should have no affect on your stability or security.

I am Autistic, live alone, and under the current conditions of National Lockdown have had little opportunity to practise my 'inter personal' skills over the past month so apologise if I came across a little 'blunt', such is the condition.

I fully understand the nature of FLOSS, being one of it most ardent advocates. I have made small contributions in the past to a number of projects including: ProFTPd and MySQL [I still have the T-Shirt, thanks Monty!] to name but two and have used it [GNU/Linux et al] exclusively on all my personal and business devices since 1995 [Slakware / Kernel 1.2.13].

I am not in a position to make those tests this week but hope to be able to get back to you with the results a week on Monday [20th April].

Resetting severity to default of --.

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)