Thank you for your feedback.
Well, technically I can get more items at the start. I don’t have an exotic use case that prevents me from doing that. I’m thinking more in terms of general robustness and scalability of the plugin.
The problem is that I have to “guess” how many initial items are enough. If some user has a really high-resolution display and I didn’t anticipate this during development, the UI breaks for that user.
So either I use a fixed value for initial array size that may be way too large for small screens (meaning bad response time) and possibly still to small for some very large screens (breaking the UI) … OR I somehow calculate the necessary minimum number of initial items dynamically, which isn’t easy and rather error prone. It would be nice if the plugin could do that by itself.
So to sum this up, I don’t think this is an edge case at all. But maybe I’m just thinking too complicated, and there’s an easy solution?