Fabricio Matte

The problem is that ng-sortable intentionally removes the native touch scroll behavior from `as-sortable-item`s as you can [here](https://github.com/a5hik/ng-sortable/blob/7d0e9da06f1fa83369cdf403de0544df917a2c36/source/ng-sortable.css#L9-L14). I believe that does not make much sense when you are using...

@shama how's the progress on the builds packaging? I've just noticed that I could rollback to `0.5.1` after I had already successfully installed Gaze 0.6.4 (by installing MSVS C++ 2012...

@shama thanks for the quick response! I just saw that you've added the [pre-built binaries](https://github.com/shama/gaze/commit/aa494d0657af96337168c61c8a57f0229ae8d440) after posting my previous comment, thanks for the awesome work. `:)`

> IMHO, I think we need to provide a way for developers to decide what should happen. 👍 There are several use cases and no "one size fits all" solution,...

Nice! Very throughout explanation. 😄 I'm just not sure what's the use case for responding with a cached version when the resource is not found (404). If the request reaches...

Well, I thought you were talking about a 404 response—if you get a 404 back then it means the connection to the server is working and the resource doesn't exist...

I guess we may be having some communication problem. Let's try again. > Well, it may still exists but your device may have lost its connection. Here you are talking...

To be more clear, your [comment above](https://github.com/NascHQ/dsw/issues/18#issuecomment-246876867) mentions handling 404s with cached responses, but then you said the cache would be used to allow the page to work offline. This...

> The two situations you mentioned would be for failed requests when offline, and failed requests for non-existing pages. Yes, exactly. > If the requests fails with a 404 (let's...

> I think the discussion is more about the default 404 behaviour. I guess you mean "default fail behavior", right? I'm not sure if 404 qualifies as a failed request,...