Let me provide some background information about the current implementation of the MobileListView events.
- dataBinding and dataBound are fired only when virtualization (endless scrolling) is disabled
- itemChange is fired only when virtualization is enabled
The reasoning behind this approach is the following:
- dataBinding and dataBound are normally associated with refreshing of all rendered items of a Kendo UI widget. Such a refresh does not occur in virtualized mode, when only some items are removed from one end and appended at the other end, while scrolling. The Kendo UI Angular integration relies on widgets' dataBound events to recompile the item templates, and if the dataBound event is fired in virtual mode, this will recompile templates that have already been compiled, which is not necessary.
- dataBound assumes that all widget items are freshly rendered, so customizations may be required by all of them. On the other hand, itemChange is fired for specific items.
Since the itemChange can be fired multiple times in virtual mode, it is possible to use event throttling to hide a loading indicator.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI