Show HN: PullToRefresh.js (boxfactura.com)

What does that mean?

The use case we're aiming with this library is that not always you want to refresh the whole page; sometimes you want to update just one section of the app (think Gmail), do something deferred with a worker, or set a timeout.

Also, you want to be consistent across all browsers/platforms, and maybe add a little touch of personality or branding [1].

So, while I agree with you it should be standard, and maybe it should have an API, it has to be flexible enough for every and each thing you want to achieve... so you'll need a library, and we're full circle.

1: https://muz.li/blog/refresh-inspiration/

http://www.ipwatchdog.com/2015/02/25/the-road-forward-for-so...

Also, what I said in a previous comment: maybe you want consistency across browsers/platforms or branding, customizing how it looks. And maybe you don't want to refresh the whole page, maybe just one section calling a JSON API, or perhaps you have a heavy job that requires a worker.

I'd suggest you to download the library and delete some of the lines for the callbacks on the touch events, maybe you can isolate it and figure out what is achieving that result.

Or, you could try something like this:

    PullToRefresh.init({
      mainElement: '#main',
      distMax: 0,
      onRefresh: function(){}
    });

That's not an anti-feature, that's poor UX. If you're entering data into a form that might get lost, the UX team should add an event that checks if you're trying to go somewhere else (or reload), to confirm whether that's the action you want to do.

Your argument against pull to refresh could be the same for the reload, back and forward buttons in your web browser. Also, against the URL/search bar, because it might lose your progress.

And all is fixed with a confirm() on the unload event, and it has nothing to do with the pull to reload feature.