We are aware, and it certainly wasn't intentional. Waiting for fix in our impl of Material Design Lite (ironically before we move off it)

What are you gaining by replacing the native scroll functionality?

Are you trying to add "standard Android scrolling inertia" or something? I mean you must be trying to change something, or will I not notice it when it's working?

We didn't replace anything, there seems to be a bug in Safari that we have to work around with a translatez() hack.. should be fixed now.

Sorry for the insult... but you guys really should have tested this across browsers before it even shipped.