All Products Community Forum

I need to have a telecon from the provider meet.goto.com using Firefox on my PC running Linux Mint mint-001-1.0 147.0.1 (64 bit) but I get an error message browser not supported. What can I do? Thanks

I am running the latest firefox version 147.0.3 64-bit. Gmail opens and runs fine on duck duck go and brave. Cannot find any info on how to solve/fix/override/whatever on "numeric code 4" but seems like other folks experience, too. I appreciate your help.

Since a couple of days we get the announcement F1TV.formula1.com/nl/ is not compatible with this browser Use an other browser or hardware many Years there was no problem

The website commonly used by Arizonans to make filings for court, will not work properly with Firefox, even after turning off Enhanced Tracking Protection. I had to use Chrome instead.

I need my gmail account but I cannot sign into it, it wants me to start a new one, but that will not do at all. I will wait for a week to see if you can rectify this problem.

Dear Mozilla,

As a long-time Firefox user and evangelist, it saddens me that the time has come to part ways.

I have seen threads from others commenting on Firefox's aggressive memory consumption and retention. I have not measured this and thus do not feel qualified to comment, but, sadly, I am not surprised.

My own experience in recent times highlights 2 events that have driven me here.

1) Several websites just not responding in that some screens will not even scroll. This is fixed by me moving to a different browser.

2) More seriously - When trying to fill in a web form for a work job application the page was completely unresponsive. When I contacted the web site support their answer was: "Are you using Firefox? Ah, Yes, we are having issues with Firefox that we are trying to resolve. Our suggestion for the time being is, if practical, try using a different browser". That answer worked.

I should add that the usual cache clearing, machine restarts, even Firefox reinstall did nothing to fix either of the above issues.

So with the serious memory greed issues reported by others and my own (dys)functional experiences, I fear the time has come.

Thank you for the last 30 years or so and I am sorry it has come to this.

Best of luck in your future endeavours.

BTW - This post was entered using a different browser.

hi i just install firefox and when I use messenger and put my cursor on camerra or phone I have the message voice- video call not available on this browser can you help?

Summary: Uploading a file to a custom webapp with Chromium (Edge) works but consistently fails in Firefox. In Firefox the request is created, and times out. The server receives no file and logs “missing file.” The same webapp code is running on both Chromium and Firefox.

Environment:

• Next.js app (pages/api route)
• Endpoint: POST /api/file-upload
• Client: fetch(url, { method: "POST", body: FormData, credentials: "include" })
• Server: export const config = { api: { bodyParser: false } } + multipart parsing (formidable)
• Edge/Chromium: Version 141.0.3537.85
• Firefox Version 147.0.3 (64-bit)
• OS: Ubuntu 22 / Linux

Steps to reproduce:

1. Create a FormData object and append a local file:

  const fd = new FormData();
  fd.append("template", file, file.name);
  fetch(`/api/file-upload`, {
    method: "POST",
    body: fd,

1. In Edge/Chrome, upload succeeds. Server receives multipart body and parses the file. Actual behavior in Firefox:

• Transferred: 0 B
• No response status/body
• Client times out (Upload times out)
• File upload request received
• No bytes read server‑side.

Evidence:

• Edge request logs:
  • content-type: multipart/form-data; boundary=----WebKitFormBoundary...
  • bytesRead ~1.69MB
• Firefox request logs:
  • Transferred 0 B
  • File upload missing file field

Notes:

• Client FormData is valid; we log file.name and file.size right before fetch.
• There is a CSP report‑only warning (frame‑ancestors) when using a fallback iframe approach, but we are not using iframe in the failing case.

Question: Is there a known issue where Firefox blocks or fails to send and multipart/body can be stripped before it leaves the browser? Is there a recommended workaround that does not rely on browser sniffing?

Moderator note: This question has been edited to correct the formatting.

There seems to be a glitch that I keep encountering when trying to sign in through my TV provider, particularly Verizon, to watch DisneyNOW or TCM or any other service for that matter. The website known as "ssoauth.verizon.com" seems to keep hanging on the message "Please wait - we are verifying your account," and the sign in never gets completed. I already tried clearing my cache and history but with no result.

Even trying to submit troubleshooting information is causing the form to crash here. If you would like, I can send you a text file containing the log I saved from the browser console.

I know that messenger is going away on he desktop as per Meta. Ever since i have had Messenger through Firefox when i click on the camera and the voice it say it can not be done on Firefox browser. Why is this why does it not come up on Fire fox. You at firefox are going t force me off this browser. please explain