Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why does the new Quantum take so long to type and pullup a wedsite?

  • 3 பதிலளிப்புகள்
  • 3 இந்த பிரச்னைகள் உள்ளது
  • 16 views
  • Last reply by TX713

I got the update for the new Quantum browser and it is terribly slow. It delays the type, it delays when I click to open a new window, and is very slow to open a site. Any ideas?

I got the update for the new Quantum browser and it is terribly slow. It delays the type, it delays when I click to open a new window, and is very slow to open a site. Any ideas?

தீர்வு தேர்ந்தெடுக்கப்பட்டது

i've received some info via pm.

please see if this fixes the problem for you: go to the firefox menu ≡ > options > privacy & security panel and under permissions check the setting to prevent accessibility services from accessing your browser.

Read this answer in context 👍 1

All Replies (3)

hi, could you go to the firefox menu ≡ > help ? > troubleshooting information, copy the contents of that page and paste them here into a reply on the forum (or if it's to long through a site like https://pastebin.mozilla.org/ and provide the link here)?

this might give us a clue what is going on. thank you!

தீர்வு தேர்ந்தெடுக்கப்பட்டது

i've received some info via pm.

please see if this fixes the problem for you: go to the firefox menu ≡ > options > privacy & security panel and under permissions check the setting to prevent accessibility services from accessing your browser.

That seems to solve the problem, thank you.