Rohan Deshpande

> A possible API could be to allow an argument to be passed to refresh that would retain any previous data until the new fetch completes. So if I understand...

Right! Okay, I think we _did_ discuss this @albertogasparin, I think it shouldn't be too hard to add and I feel it might be a fairly common requirement from consumers.

I think JSDOM is currently still a hard requirement

Yep. Resources are requested immediately on transitioning into the next route as long as they have not been previously cached and are outside the `maxAge` value.

Would probably need a codesandbox or something to see what is going on here, the package does have a `main` property

Builds are failing here. I'd also appreciate it if you could add tests to cover functionality impacted by this change to assert that behaviour is identical before and after.

Hi, I'm trying to implement this, have pulled your commit into my app, but I'm not exactly understanding how the native dragula behaviour is being stopped by this. I can...

@ben-girardet Hmm I guess what I'm saying is, Dragula itself fires the `grab` handler, how are you preventing that default behaviour? In any case I've also made a PR for...

@redaxmedia this prevents scrolling the container entirely though.

What mobile browsers are you testing on and what version of the operating system? Can you post a fiddle or codepen as an example? I’ve tried this out and it’s...