[disappeared]After update, scroll function changed. Want the old paradigm back.
Laptop: Dell Inspiron 1545 OS: Kubuntu 13.04 Firefox: 24 Mozilla Firefox for Ubuntu canonical 1.0
What I have now: I press the arrow keys on the laptop (these are dedicated arrow keys, not multifunction keys), and the whole screen slams to the bottom (press down arrow key), or to the top (press the up arrow key).
What I expected: I expected no changes from what I had before - a smooth scroll of a few dozen pixels per second (not actually measured), i did not want a top slam or bottom slam. I already have dedicated keys for 'home' and 'end' which are elsewhere on the laptop keyboard (also dedicated keys, are not multifunction), so my expectation for the arrow keys is that the earlier smooth scroll functions would remain unchanged.
Somewhere since early August (give or take, I've been busy), I updated to Kubuntu 13.04 from 12.10, and I have updated the packages a few times. I remember that before these updates, the arrow key as a scroll function was what I had been using since I owned the laptop, it worked fine before, I know I hate what scroll is doing now. I have not modified about:config, but would do so if it comes to solve the scroll.
I've visited the KDE Control panel for the trackpad/mouse settings, nothing seems obvious. I know Kubuntu/Ubuntu slammed a LOT of system changes on me in this update, so I really haven't any way to be certain of the location of the needed changes... maybe the issue is not Firefox, but FWIW, I have scrolling issues on another Firefox installation and want that issue solved as well (this one request might fix both scroll issues).
Where could I turn to solve this?
この投稿は mmmmna により に変更されました
すべての返信 (7)
hello, please press F7 in order to leave caret browsing mode - then the behaviour should be back to normal...
Note: issue is NOT caret browsing, no need to send me to https://support.mozilla.org/en-US/questions/969787?esab=a&s=caret&r=2&as=s
It does the slamming thing both caret on and caret off.
この投稿は mmmmna により に変更されました
Nope. Tried it both ways, same slamming.
ok, i can only replicate the behaviour you've mentioned while in caret browsing mode - but i'm on windows, so i don't know if your system updates could have to do anything with this unwanted change.
on thing you could try though is to run firefox in safemode once and see if the same issue is occurring there...
Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems
Rename or delete the prefs.js file and possible numbered prefs-##.js files and a possible user.js file to reset all prefs to the default value.
Create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
- https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer some files from an existing profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem.
The ONLY thing I have done is toggle caret browsing between 2 states, it was off when I first tested caret browsing for this thread (which means it was not part of the initial situation which I posted about), I turned caret browsing on to test it and I still had the slamming problem; I returned caret browsing to off, I still had the scroll slamming.
Since I last posted, I put the laptop into sleep mode (closed the screen over the keyboard), I worked an hour outdoors, I then awoke the laptop to check this thread, and now scrolling is normal. Seems that the problem has 'suddenly gone away' since the laptop slept.
To the reader: caret browsing made no difference: it was off when the problem occurred, caret browsing turned on still slammed, caret browsing turned off after the testing still slammed.
FWIW, prefs.js changed around (I kept no records of timing) the time that I toggled caret browsing, but as I stated above, caret browsing made no difference when I tested both of its modes.
Does caret browsing need time to take effect? Does caret browsing need to have FF backgrounded then foregrounded? Did toggling caret browsing change something in my preferences or in the FF config file? I see ~/.mozilla/firefox/vr8blhii.default/localstore.rdf changed since I slept the laptop... isn't that file related to plugins?
My networking gets disconnected a few moments after I sleep the laptop (BUT: I have slept the laptop dozens of times this week alone, the scroll slamming was never diffrerent until just before this post)... does that force any events inside FF? The OS settings were not changed since a few days ago, so the OS is not at fault.