4 ms·
I don't get this. From http://joehewitt.github.com/scrollability/ http://joehewitt.github.com/scrollability/: "Native scrolling for mobile web apps... or at lea
by hpaavola 15y ago
I don't get this. From http://joehewitt.github.com/scrollability/ http://joehewitt.github.com/scrollability/: "Native scrolling for mobile web apps... or at least the closest thing to it!" How does my Android phone lack "native scrolling" and what does that mean?
- ZeroGravitas 15y agoOn iPhone, scrolling in an app, and a web page/app, are different in terms of speed and inertia. There's been several attempts to emulate the "native" scroll response via javascript so that web apps can more seamlessly replace alternatives.
- nupark2 15y ago> ... so that web apps can more seamlessly replace alternatives. One native feature down (at least until Apple evolves it again), countless pile of more features to go. This is a losing battle.
- masklinn 15y ago1. It's for web applications, with all that implies: the ability to scroll only sections on the screen (not the whole page) while still having the right physics, lazy loading, snapping (the horizontal demo implements "snapping" transitions similar to iOS's springboard) 2. It implements iOS's UITableView physics, which are different (smoother) than Safari's native
- hpaavola 15y agoSo by "Native scrolling for mobile web apps" he means better scrolling of iOS Safari in general and especially for elements that have overflow:scroll styling.
- masklinn 15y ago> So by "Native scrolling for mobile web apps" he means better scrolling of iOS Safari Well he means what he says: scrolling which looks and feels like native (UITableView) scrolling.