搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Has Google declared war on Mozilla ?

  • 22 回覆
  • 2 有這個問題
  • 22 次檢視
  • 最近回覆由 wealstarr

more options

Hi,

I was using Maxthon browser but I switched to Firefox yesterday and the first things I noticed is that Google Captcha, on Firefox is not just difficult, it's brutal. I did a search to see if it was just me and indeed people on different boards were complaining about Captcha being more difficult on Firefox. It's almost impossible to do multiple Captchas, I'm currently running both Firefox and Maxthon to get around this Google policy.

I switched back to Chrome and it was back to normal. Just select three images and you're off. Also, the images loaded with a blink, like they should but on Firefox they take about 1 to 2 seconds to load. And Captcha alsways reloads regardless of how accurate my input was not twice but thrice. I also checked it with the Internet Explorer and it's fine there too.

I tried changing my useragent to chrome but Google beats me to it. Every other site detects my Firefox as Chrome but Google still detecting it as Firefox (in URL's "Client=firefox")

I have no virus, malware. My machine is clean. And I don't use any VPN, proxy, TOR etc.

Now I've got three questions:

1- Is this prejudice based on some real genuine threat that Firefox poses or is it just business as usual ? 2- Is Mozilla aware of this ? What are they doing to resolve it ? 3- What can I do to resolve it ? Is there a solution to this problem ?

P.S Even you don't wanna answer the questions, I would still appreciate your feedback on this issue.

Thank you for reading.

Hi, I was using Maxthon browser but I switched to Firefox yesterday and the first things I noticed is that Google Captcha, on Firefox is not just difficult, it's brutal. I did a search to see if it was just me and indeed people on different boards were complaining about Captcha being more difficult on Firefox. It's almost impossible to do multiple Captchas, I'm currently running both Firefox and Maxthon to get around this Google policy. I switched back to Chrome and it was back to normal. Just select three images and you're off. Also, the images loaded with a blink, like they should but on Firefox they take about 1 to 2 seconds to load. And Captcha alsways reloads regardless of how accurate my input was not twice but thrice. I also checked it with the Internet Explorer and it's fine there too. I tried changing my useragent to chrome but Google beats me to it. Every other site detects my Firefox as Chrome but Google still detecting it as Firefox (in URL's "Client=firefox") I have no virus, malware. My machine is clean. And I don't use any VPN, proxy, TOR etc. Now I've got three questions: 1- Is this prejudice based on some real genuine threat that Firefox poses or is it just business as usual ? 2- Is Mozilla aware of this ? What are they doing to resolve it ? 3- What can I do to resolve it ? Is there a solution to this problem ? P.S Even you don't wanna answer the questions, I would still appreciate your feedback on this issue. Thank you for reading.

被選擇的解決方法

Hi the-edmeister

I apologies I couldn't find the solution for the original issue of captcha being more difficult on Firefox. However the awesome support team here helped me with every other thing like cache size.

I think the issue can't be resolved by just changing any settings so the users/contributes can't do much about it. It has to be taken to the development team. Just my opinion.

Kind regards.

從原來的回覆中察看解決方案 👍 0

所有回覆 (3)

more options

Okay all sorted out. A big thanks to all the contributes for helping me out.

@Mods: Please close the thread.

more options

Please let us know what your solution is. Might be helpful for other users who experience the same issue.

more options

選擇的解決方法

Hi the-edmeister

I apologies I couldn't find the solution for the original issue of captcha being more difficult on Firefox. However the awesome support team here helped me with every other thing like cache size.

I think the issue can't be resolved by just changing any settings so the users/contributes can't do much about it. It has to be taken to the development team. Just my opinion.

Kind regards.

  1. 1
  2. 2