We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

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

了解更多

Since Win 10, every mouse and keyboard input in FF takes 2 secs. to take effect.

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 MrWonderful

more options

Since installing Windows 10, it takes a full second or two for a scrolling move (e.g.) to take effect. I'll turn the scroll wheel, and it will take 2-3 seconds for the page to actually move. Same thing waiting for a neutral cursor to turn into a "live" hand. In fact, I'm writing this via Chrome, since FF has becomes so slow and frustrating.

Since installing Windows 10, it takes a full second or two for a scrolling move (e.g.) to take effect. I'll turn the scroll wheel, and it will take 2-3 seconds for the page to actually move. Same thing waiting for a neutral cursor to turn into a "live" hand. In fact, I'm writing this via Chrome, since FF has becomes so slow and frustrating.

被選擇的解決方法

What is your computer system and Firefox?

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

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

所有回覆 (2)

more options

選擇的解決方法

What is your computer system and Firefox?

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

more options

I didn't have to do this, because a different solution worked--re-starting FF. Thanks.