(no title)
gernb | 3 years ago
Actually though, I absolutely hate that Chrome iOS has pull-to-refresh. I've never in my life wanted to refresh a page by pulling and instead what happens is once or twice a month I'm filling out a form or typing a post and I need to scroll up. I do it instinctively, chrome refreshes, I lose everything I just typed. Thanks Chrome
Me1000|3 years ago
It was originally "pull to load newer posts". Remember that a twitter timeline would have the newest posts at the top and the older posts below it. So when a user would return to the app, they would keep scrolling up until they reached the top. Then if they kept scrolling triggering the iOS rubber-banding behavior, it would load newer posts. Then the newer posts would be rendered above where you were in the list.
Refreshing the whole page wasn't the intended purpose.
amatecha|3 years ago
One fundamental point of the interaction is that you're already scrolling to the top of the list because you're viewing a reverse-chronologically-sorted list of network-driven content. If, after hitting the top of the list, you keep trying to scroll up, you're already suggesting to the software that you want to see more. On a website, this implication doesn't apply. I'm just trying to get to the top of the page.
pornel|3 years ago
BTW, the Firefox-flavored Safari skin has a regular refresh button.
kitsunesoba|3 years ago
madeofpalk|3 years ago