derek / scrollview-sandbox Goto Github PK

Steps to reproduce:

1. edit dualaxispaginator/index.html to expose the s global for easy console manipulation
2. open dualaxispaginator/index.html
3. perform a vertical drag gesture on the lower scrollview (text)
4. from console run s.pages.set('index', 1) or s.pages.scrollToIndex(1) and notice how neither work and if you try to interact with gestures it will become confused

A workaround from the integration side is to either delete _gesture or reset _gesture.axis to the pagination axis (in this case x).

This seems to be symptomatic of keeping _gesture around long past gesture end and I think we would be better off storing just the relevant bits from a gesture needed for the transition and nulling it out -- combined with better checks for pagination axis when sv.pages.set('index', N) and sv.pages.scrollToIndex calls are made.

I still hope to dedicate some time to looking at this as well but figured it would be good to open an issue for tracking purposes.

Lots of testing has shown that while the visibility:hidden toggle does help to free up memory it doesn't help enough with touch responsiveness -- and to date a "treadmill" approach has shown to be the most promising.

Treadmill -- add/remove page nodes as necessary to maintain only a small subset of pages in the live DOM, thus creating a much smaller canvas for dragging and animating.