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

SHIFT KEY ACTING LIKE THE BACK BUTTON

  • 3 replies
  • 4 have this problem
  • 20 views
  • Last reply by philipp

more options

On any website through Firefox the shift key acts like the back button. When using Chrome this does not happen. This just started yesterday 8/21/2014, I rarely use Firefox, just for school, so I have not added any add-ons. Please advise, and thank you for your time :) BTW I had to use Chrome to send this, when I was setting up my account I could not use the shift key for my email address.

On any website through Firefox the shift key acts like the back button. When using Chrome this does not happen. This just started yesterday 8/21/2014, I rarely use Firefox, just for school, so I have not added any add-ons. Please advise, and thank you for your time :) BTW I had to use Chrome to send this, when I was setting up my account I could not use the shift key for my email address.

Chosen solution

hello Angelina1204, in the past we have had similar reports by other users with a defective mouse (or mousepad), since shift+scrolling is a shortcut to go back/forward in the history in firefox.

to circumvent that, please try the following: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named mousewheel.with_shift.action. double-click it and change its value to 0.

Read this answer in context 👍 1

All Replies (3)

more options

Chosen Solution

hello Angelina1204, in the past we have had similar reports by other users with a defective mouse (or mousepad), since shift+scrolling is a shortcut to go back/forward in the history in firefox.

to circumvent that, please try the following: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named mousewheel.with_shift.action. double-click it and change its value to 0.

more options

But why did this just happen all of the sudden?

more options

again, it's probably a hardware issue - maybe one of the sensors is suffering from wear and tear