In my project (not the sample linked), I was able to work around this issue by calling stopPropagation on the touchmove event for scrollable content. However, it would be great is Bespoke could handle this itself.
I might take a stab at a solution if I have time, but I at least want to report the bug and get it on your radar.
Hi, thanks for making Bespoke.js. I found an issue with Bespoke that you can see here: http://jeremyckahn.github.io/bespoke-bug/public/
When I test this on desktop Chrome, the overflowing content can be scrolled as expected. On iOS, the content cannot be scrolled. This is because Bespoke is catching the
touchmove
event and preventing the default behavior. This logic breaks all overflowing, scrollable content.In my project (not the sample linked), I was able to work around this issue by calling
stopPropagation
on thetouchmove
event for scrollable content. However, it would be great is Bespoke could handle this itself.I might take a stab at a solution if I have time, but I at least want to report the bug and get it on your radar.