Other problems exists even on newer browsers, such as the absence of a scrolling position indicator in Android browsers as pointed out here.You could achieve this on Android with a library, but beware of the uncanny valley. On iOS, you will have the bouncing effect native to the platform, but not on Android as the native browser UX does not include this bouncing effect (which is weird because this effect exists in other parts of the OS UX, such as settings).Also, on iOS, scrolling is much smoother than an Android, even though the situation got better with newer devices and Android 4.0+ (it was painfully unusable in most heavy populated views before that). please notice that while the momentum effect is active by default on android & iOS, it's the platform specific momentum that will be applied : they differ from one another, contrary to a JS polyfill that makes scrolling momentum platform-independent.UPDATE : I should have done this before posting my answer, but I just tested the fiddle on my Nexus4 and your code does work in Chrome : which probably mean that you tested on an older device without Android 4+ or with a browser that did no support the overflow property ? If not, you may have made a mistake in your fixed positing or some other css layout property ? (inherited body props etc). On your scrollable content (you don't need to specify "overflow-x:hidden" if using auto property). Now for your situation, if you only want to support Android 4+ & iOS5+, you should be able to make it work both with momentum using only fixed positioning and overflow: auto More recently, the Financial Times team published the FTScroller library that looks also promising. To respond to this, as you have already pointed out, there are fallbacks such as iScroll or more recently, Overthrow that you may handle better the native implems and JS fallbacks. To get a better grasp at this, you could read this. The situation is complicated, and may mot be a problem for iOS where most devices are on iOS 5 or 6, but it is a real problem with Android fragmentation. Talking about the general problem of scrolling in mobile WebApps, scrolling & momentum on mobile browsers are a pain as there is a wide variety of different implementations depending on the platform : Android browser != Chrome != Safari != opera etc, and Android < 3 does not support scrolling as well as newer versions, just like iOS < 5. Sorry for digging up an old post but as there seem to be no satisfying answer I thought I would add my 2cents for anybody ending up here like me. However this did not work for me, although the scrolling sections worked (after I had modified the Modernizr css-overflow-scrolling test to return true for this version of Chrome) the momentum effect of the scrolling was not present. So it would seem that if you are having issues with the scrolling not working as expected then adding z-index: 0 to the element with overflow: scroll then this may help. (This behavior, behindĮNABLE_ACCELERATED_OVERFLOW_SCROLLING, is currently enabled only onĪndroid.) The obvious fix would be to set z-index: 0 on only Non-hidden elements with that property creates a cascade of stackingĬontexts below it. So the behavior of setting z-index: 0 on all Tien-Ren observed while debugging 162363 that -webkit-overflow-touch This was also compounded for me by the fact that due to this change the current Modernizr test for this feature now returns false, so my CSS styles were not being applied.ĭigging around I found another issue that discusses the support for overflow scrolling touch: I am currently experiencing this issue after updating to the latest version of Chrome for Android. Try adding z-index: 0 to the element with overflow: scroll to create a stacking-context that provides a hint to Chrome to use the fast-scrolling code path. Does not work and evaluates to false on Chrome version.Works and evaluates to true on Chrome version 469.Nexus 7 tablet running Android version 4.2.2 -webkit-overflow-scrolling: touch Īnd !!('WebkitOverflowScrolling' in ) It's very frustrating that Google appears to have removed this feature from their browser …. Maybe the beta version is not offered for Nexus 7 tablets?Īny help on this matter is much appreciated. Was support for overflow scrolling removed from more recent builds of Chrome for Android? Is there an equivalent or comparable alternative momentum scrolling mechanism (not iScroll, etc.) that I can use found in the newest version?Īs well, I searched for Chrome Beta in the Play Store on my device and it does not come up in the search results. In addition, the following evaluates to false: !!('WebkitOverflowScrolling' in ) I updated to the newest version of Chrome for Android on my Nexus 7 tablet and … -webkit-overflow-scrolling: touch
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |