![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Facebook scrolling out of control
Currently @ Ver. 102.0.1 Problem remains. Since the update to 102.0 my Win10 PC has problems with the page update. When the scroll slider gets near the bottom the page, new images begin to load. This reload results in 3-15+ newly loaded Fb posts scrolling past so fast as to be invisible. I have to keep my cursor on the scroll slider and, when the loading begins, start scrolling up if I want to have any chance to easily find the last post I was reading. I have seen this behavior, grossly exaggerated, when I was viewing a video. The reload caused the viewing to pause and upwards of 15 newly loaded posts scrolled past in this rapid manner. My work requires that I am able to view pages of Facebook posts and this is now massively time-consuming and intolerable. I may have to change browsers in spite of my reluctance to do so.
Всички отговори (13)
...and now when I try to post a comment in an existing post, the scroll jumps down a post or two when I type the 1st character instead of up a few posts. 8-/
Helium2, I think that one of the things that it means is that in FF104 they have added a "scroll-snap" series of properties that can be modified.
If you are feeling brave, you could go to about:config, search for "scroll-snap", then experiment with modifying the values? Starting with changing just the scroll-snap-stop value? Possibly with a Firefox restart after a change?
I have absolutely no idea if this will help, or if it might create problems on other sites. But it is a possible solution.
If you go down this route, make sure to note the default values of any settings you change, so that you can restore things back if needed.
With any luck though, simply toggling the scroll-snap-stop value, might see an improvement.
But of course no-one would blame anyone for not wanting to mess around with about:config. It is an advanced solution, and messing with the wrong settings can cause problems.
TechHorse > Thanks for the additional info! I've modified about:config in the past with good results, but I'm very careful with modifying things I'm not sure about. When I have the time to recover from what ever tar pit I may create I will take a look and see what's what. Maybe, in the meantime, someone knowledgeable will play with the settings and have recommendations. Thanks again.
wow today the 30th really jumping posts like 4 at a time. I wish Firefox and Facebook would get it together. It appears that Firefox can not or does not want to fix the issue. It is frustrating
The problem is not solved yet
Sorry to hear it. Posting this in Firefox 104.0.2. I decided to wait until someone had explored about:config ( that TechHorse posted about a few comments above ^ ) to see if something had been changed. I've just checked Facebook and the jumping continues.
- If there is a solution buried in about:config it seems that Mozilla's attitude is: " We have provided a way for the code savvy users to alter the Firefox scrolling response. It's no longer our problem. "
It sad that I have to spend my spare moments trying figure out how to customize Chrome to get the necessary functionality that I once took for granted with Firefox. >8-(
The problem that I call Jump Scrolling on Facebook has gone on much too long. I much prefer the Firefox browser, but I have reluctantly switched to MS Edge because of this issue. I've seen posts that this is a Facebook issue. Perhaps, but the Edge browser doesn't experience the problem. Is there no coordination between FB and Mozilla to fix this? PLEASE, . I'm about to throw in the towel and switch.
George Butch Plantation, Florida.
I agree emphatically. I am almost at the point where I finally have Chrome mostly customized for my use. My spare time for this has been very limited.
- I have tried a handful of other browsers and the scrolling problems only exist with Firefox. If this is a Facebook problem then Facebook must be waging war on Mozilla (only!) to drive Firefox out of business. It's working as far as I'm concerned.
- Aside from the original problems, another issue is occurring that I may have mentioned previously: When I begin to enter a comment in a post in Facebook, the page constantly jumps down 2-3 posts so I am unable to see the comment box I am using, and I have to scroll up to see what I am actually typing. Another frustrating issue that Mozilla is ignoring.
- One has to assume that Mozilla is not purposely trying to sabotage Firefox by not resolving these glaring problems, so the conclusion has to be that the Firefox coders are unable to resolve the issue that every other browser has solved.
It's sad to see Firefox go the way of Netscape. RIP
While Firefox seems to have the scrolling problem, Facebook is acting up in other ways on both Chrome and Firefox. This is clearly Facebook changing their coding. I'm not sure this is really a Firefox problem so much as Facebook constantly changing things.
Facebook is acting up on all browsers but yes see it more on Firefox. It is getting to the point where it will force me to change browsers and i have been with Firefox since the beginning. I have found no way to contact Faebook that really helps
ddaveleft> I have found no real problems that exist with Facebook and Chrome ( the only other browser I have spent any time with recently ). I'm not saying there are no issues, but none so obvious as the scrolling issues with Firefox have shown themselves to me in Chrome.
Mozilla made some sort of modifications to about:config to deal with the scrolling issues, I have heard, but without tutorials for how to use these mods ( if they do exist ) I am ignorant as to how to apply them.
Mozilla's failure to really address this issue in a public manner seems to show a lack of concern the dissatisfaction by Firefox users. Whether or not this is a valid interpretation by we users, it is resulting in users leaving Firefox for other browsers. That should be a main concern of Mozilla.
My FF is 105.0.3 and since it last updated, the problem seems to be worse. Has anyone found a solution?
Has anybody seen an improvement since the advent of Ver. 106.0.2 ??