Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

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

  • 2 trả lời
  • 1 gặp vấn đề này
  • 11 lượt xem
  • Trả lời mới nhất được viết bởi 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.

Giải pháp được chọn

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

Đọc câu trả lời này trong ngữ cảnh 👍 1

Tất cả các câu trả lời (2)

more options

Giải pháp được chọn

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.