> It's important to remember that Chrome (on non-Android platforms)
Chrome on Android also implements scrolling manually. Just since Android is open-source they can pretty trivially port the platform's code to their system to stay in sync rather than reverse-engineering the curves.
Right, and I'm saying Mozilla already failed at reproducing OS scrolling behavior once. Hopefully different people are working on it this time.
I wrote the first version of the Android scrolling code and also the first version of the WebRender scrolling code so, uh, sorry to disappoint you, but I'm still working on WebRender.
(Keep in mind that back in those days—the days of Froyo and Gingerbread—I was way more concerned with not having the whole browser crash due to absurd bugs in the Adreno 200 drivers than replicating minute scrolling details. Times change.) :)
Well, you're older and wiser now, that's gotta count for something :) BTW WebRender is absolutely the most exciting thing going on in browser dev right now, I can't wait for it to be ready.
While I love using Firefox on Android (I currently use the Nightly builds), the scrolling still is problematic.
Can someone explain what's wrong with the scrolling? I use Firefox on Android regularly, and haven't noticed any problems with it.
Who said it was going to be easy? :)
> I'm not saying it's the wrong decision, but know that you are signing yourself up for not just a ton of work now, but also a ton of work in the future to match platform changes.
It's important to remember that Chrome (on non-Android platforms) and Firefox already implement scrolling manually. This isn't anything new.