I’m observing an strange firefox behavior when I scroll the page using the mouse wheel. It goes back and forth through search history. So I googled a little bit and found that the KVM switch that I’m using it’s producing bogus key press event that firefox misinterprets. If you are running Linux the solution is simple as you can modify the X server configuration to ignore those events. But I cannot find a suitable solution for Windows.
Disabling history scroll in firefox (Usually triggered with Shift-<Wheel>) in about:config seems to have no effect in stopping this weird mouse wheel behavior.
Theorically changing the value of all mousewheel.horizscroll.with∗.action and mousewheel.with∗.action entries to 0 disables moving back/forward in history using the mouse wheel. Check this to know more about the meaning and purpose of mousewheel.∗ entries. But as I said It seems that doesn’t make any difference.
If you know the solution for this problem post it in the bug report
Tags: back, firefox, forward, history, mouse, scroll, scrolling, wheel
hi, found this link, may help..
< http://strabes.wordpress.com/2007/04/01/disable-firefox-going-backforward-on-horizontal-scroll/
Well, as I said in the post changing the value of all mousewheel.horizscroll.with∗.action and mousewheel.with∗.action entries to 0 seems that doesn’t make a difference in this context. I mean, when using a KVM switch.
as i had the same problem and reading about the KVM or maybe not a KVM .. after changing values which totally stopped my scrolling i put them back and tried one simple step which solved all the problem… Unplug the mouse from the KVM and plugged it back in… no more problems.
I also use a KVM switch and the problem began manifesting itself a few days ago. Unplugged and replugged mouse (to KVM) and have been problem-free for hours.
Hooray! You guys posted the solution to a problem that was driving me nuts!
After fruitless fiddling around in the about:config, I’d have never even thought of wondering about the KVM.
As suggested, unplugging the mouse from the KVM and then plugging it back in again seems to have done the trick…. well for 20 mins of frantic scrolling, at least.
Cheers!