It seems a bit inelegant to introduce a CSS property for this. Those vendor prefixes should be reserved for properties that either are in the process of becoming a standard or that the vendor wants to become a standard. I don’t know how that property fits in there, it doesn’t seem like something that should be part of the standard, it seems very iOS specific. That’s not what those vendor prefixes are there for.
What meaning would that property have on other platforms?
By the way, there’s even more good news for web apps. contentEditable is supported in iOS 5, in fact Apple devoted a good chunk of a WWDC talk to contentEditable.
it doesnt, but currently users cant scroll elements that have hidden data with overflow:scroll on either devices, this fixed it for ios, I would like to see the same fix for android.
Hm, ok. I guess the syntax rubs me the wrong way. Why does “overflow-scrolling: touch;” mean “use native scrolling”? What are the other values? What does “overflow-scrolling: touch;” mean on the desktop?
Usually you scroll the page when you touch the screen. In this case you scroll the overflowed element first when you touch. Traditionally embedded elements required two finger scrolling which was a usability kludge. You'll have to specify it somewhere and I think CSS is appropriate for this.
What meaning would that property have on other platforms?
By the way, there’s even more good news for web apps. contentEditable is supported in iOS 5, in fact Apple devoted a good chunk of a WWDC talk to contentEditable.