Thanks for the heads up. I was mostly happy the thing worked well (except for arrow-key scrolling) with js off... I wasn't aware of this (mis)feature of Firefox (I can see the rationale of using line-height for scrolling a line at a time, so it might be safe to say that the css is at fault here).
Speaking of misfeatures: I was scrolling down this page, wanted to go back up to re-read something, and the entire page just changed.
I wondered why for a second, then made a half-inch swipe to the left and discovered there's a "feature" to let me change the page for some reason, but it requires that I change the fundamental way I operate my phone/browser.
Tried to read the article again, and on the way down to where I was last reading, the page changed again. Closed the tab and won't bother reading the rest because I'm infuriated.
This is on a Nexus 5 with Android 5.1, so no, there is no rendering issue here, or lag in read of inputs. This is just an anti-feature that need not exist, nor is made obvious to the user that it exists and needs to be worked around.
