Thanks for taking the time to respond Todd.
Not just the scrollview, but responsiveness in general is slower on Android. I have read that the Android browser is not taking advantage of the GPU hardware. Maybe that will change in Ice Cream Sandwich?
You've confirmed my findings: we found some serious deficiencies in Android devices when applying certain CSS3 transforms on pages with form controls. (And it turns out that it's a CSS3 transform which is used by the scrollview component too.)
We found the scrollview so useful in our iPhone app for a layout with a permanent footer and fixed header, that we cannot do without it. Our iPhone App rocks and I believe it is a showcase of what you can do with HTML5/CSS3 and jQuery Mobile.
Imagine our complete disappointment when we discovered the 'very serious issues with forms in Android' you mention. (I suspect you've experienced the same emotion, Todd.) Our only option was to branch our code for Android - something that grated against every fibre of my idealistic cross-platform architecture strategy. :(
(I'd really like to know what Sencha did, whether it's reliable, even in Android forms, and if it can be applied to jQuery Mobile. They say they're going to be blogging about it soon.)
I am so very disappointed with Android right now, that I feel that developers of the world should know what a minefield they're stepping into. So I'm blogging about it:
http://red-3.blogspot.comGoogle cannot change the past, but they had better make the future much, much better.