It's all about "butter" vs "stutter". And as a Firefox fanboy, I'm sad to report that Firefox is on the latter end of the continuum. What you describe is my e

It's all about "butter" vs "stutter". And as a Firefox fanboy, I'm sad to report that Firefox is on the latter end of the continuum. What you describe is my experience exactly -- except that it's not quite limited to mobile. I do all my primary development against Firefox. I'm content to optimize for Gecko, and I've learned what it handles well and what it doesn't [0]. In cases where I've really doubled down to optimize some transitions, I can get almost-butter from Firefox, where Chrome and Safari are pure pleasure, seemingly no matter what I throw at them. Hell, even IE 11 is better when it comes to transitions. That said, I think Gecko looks the most beautiful for static rendering. This is less true since Chrome 38, which supports proper web font rendering for Windows, but I'll maintain that Gecko's compositor output still has a certain je ne sais quoi compared to everything else. Still, as a developer who "wants the web to win," [1] it's troubling to me that the vendors with native platforms are still outperforming in the browser space, and I hope that Servo is the dark horse that will change all that. [0] For instance, I've read this thread one too many times: https://bugzilla.mozilla.org/show_bug.cgi?id=524925 https://bugzilla.mozilla.org/show_bug.cgi?id=524925 [1] Quoting http://jlongster.com/Radical-Statements-about-the-Mobile-Web http://jlongster.com/Radical-Statements-about-the-Mobile-Web