There are two distinct problems I've noticed with FF scrolling vs. Chrome on Android.
First is that certain elements block scrolling. I use FF primarily for Facebook (since FF allows me to use my – shameless plug – idle-time faker extension [1]). If my scrolling thumb lands on the "Like" button of a post, the screen just stays put. So about 1/3 of my "scroll" gestures are in vain.
Second is that "flinging" motions don't register very well with Firefox. With Chrome, "flinging" sends the web page flying at a predictable speed; with Firefox, it lags for a fraction of a second before scrolling at a random speed which is usually much slower than that in Chrome. It's as if Firefox doesn't register the final thumb flick of a "fling", but Chrome does. Since "flinging" is my primary method of browsing longer web pages, ultimately my thumb has to physically do more work, and gets exhausted more quickly, when using Firefox than Chrome.
A third nitpick is that, while (non-flinging) page scrolling keeps up with my thumb, it does so in a jerky manner, like it can't quite keep up with rendering, or it doesn't see all the touch events. Reminds me of an old PDA. In contrast, scrolling in Chrome is very smooth. This looks ugly but I could live with it.
It is the first to two issues that prevent me from using Firefox on Android for anything but Facebook.
There are some values you can tweak in about:config, but I've never gotten it to be as smooth as Chrome. I know the FF team are well aware of the issue, but I figure all resources have been tied up by the upcoming FF57. As far as I know, WebRender will help.
Well dealing with certain sites covered in Javascript elements (YouTube comments on the mobile site comes to mind) the browser's 'memory' of clickable elements don't always update with each swipe. So tapping one element on a site ends up triggering something else on the page.
What do you mean?