fix contentinset bug

Open dylanNew opened this issue 7 years ago • 2 comments

Apr 10 '18 02:04 dylanNew

hey @dylanNew! please leave some description what exactly your PR fixes these changes looks important and could impact existing users

Oct 16 '18 12:10 rnkyr

@rnkyr I think that's because the following lines check offset against 0, but we could be setting the offset to start with an inset, so the result won't be right. A side issue is that the .initial state is never called, and when I pull half way then release there's no call back - how do you deal with cancelled state?

Dec 11 '18 03:12 hyouuu