Jonathan Ochmann

Implemented since Nightly 1.1

fixed since 1.1

Components no longer dispatch "data" events. State changes of nested reactive data structures automatically bubble to their ancestors and can be listened to via Component.state.observe()

Fixed

I ran into the same limitation and ended up writing my own micro tool for this with direction detection and a few perfomance optimizations. It allows for both horizontal and...

tbh I've never done a pull request before and don't really know how that works. feel free to adopt anything you might find useful (that's why I'm sharing it here)

I refactored and improved the approach a little by moving most of the pre-selection logic into the touchstart listener to greatly simplify the touchmove handler and further optimize performance ....

@lazd I've tested this on elements that are either horizontally or vertically scrollable, not both at the same time. I should test for that and report back.

In case an element is scrollable on both X and Y axes here's what will happen: If we're at the top or bottom end of a Y axis scrollable, that...

> Edit: Actually I'm checking for either X or Y scrollables in the above implementation, the handler would need a slight modification to allow for XY scrollable elements (if +...