I’m struggling to get the combo working with url + dataFeed + paging using a webix proxy. I’m running into three issues:
Loading the initial value in the list (e.g., using setValues() on a form or setValue() on the combo).
Correct configuration for url and dataFeed with paging. I’ve seen different approaches suggested on the forum, but the docs indicate url and dataFeed can be used in options.body (dataFeed of DataCollection, Properties Webix Docs).
How to make all of this work cleanly with a proxy (without duplicate/incorrect requests).
I’ve put together a small snippet that reproduces the problem: Code Snippet — could you help me figure out the correct setup?
Thank you for providing the detailed description. After reviewing your snippet, the behavior that you see is both a configuration issue and a limitation of the current release.
The scrolling issue is a bug and I’ve reported it to our development team, thank you. It will be addressed in one of our next releases. In the meantime, you can use a workaround provided in the snippet below. The solution is to create a custom list, that will ignore scroll request after fetching data in the proxy.
Here is the snippet that you’ve provided with the fixes implemented: Code Snippet
I’ve added input debouncing to prevent frequent requests from scrolling, and that also lets initial data to be loaded. The handleComboChange function allows for setting the value programmatically using setValue. The dataFeed function ensures correct behavior when the combo’s value is changed - it resets the scroll position and loads the next page correctly.
Hope this helps. If you have any further questions, please let us know!