2 ms·
Look closely at 0:14 - 0:18 where there are a couple of major UI hiccups in the midst of the rubber band scrolling, especially 0:16 - 0:17 where it refuses to s
by dheera 11y ago
Look closely at 0:14 - 0:18 where there are a couple of major UI hiccups in the midst of the rubber band scrolling, especially 0:16 - 0:17 where it refuses to scroll beyond a certain part of the page despite there being content further down. This resolves itself automatically at 0:19 but then the navigation bar disappears.
Also, from a UI design standpoint, to maintain consistency with everything else in the ecosystem, the navigation bar (i.e. the "entire page") should NEVER scroll or have rubber-band effects for a web app. Only scrollable divs should scroll. Yes, you can disable this in Safari with CSS, but it will still hiccup ~5% of the time.
HTML5 is supposed to be a convenient way to develop Android/iOS in one go. But it's these things that make people say "to hell with it, let's just write native iOS/Android versions" because the native UI widgets don't have these hiccups.