fix(useInfiniteScroll): re-measure arrived states when async infinite scroll resolves

[scottbedard]

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

⚠️ Slowing down new functions

Warning: Slowing down new functions

As the VueUse audience continues to grow, we have been inundated with an overwhelming number of feature requests and pull requests. As a result, maintaining the project has become increasingly challenging and has stretched our capacity to its limits. As such, in the near future, we may need to slow down our acceptance of new features and prioritize the stability and quality of existing functions. Please note that new features for VueUse may not be accepted at this time. If you have any new ideas, we suggest that you first incorporate them into your own codebase, iterate on them to suit your needs, and assess their generalizability. If you strongly believe that your ideas are beneficial to the community, you may submit a pull request along with your use cases, and we would be happy to review and discuss them. Thank you for your understanding.

---

Description

Issue: #3019

Our useInfiniteScroll composable is not working with async functions. This is caused by arrivedState[direction] never being set to false when the container is resized.

This state becomes stuck because the measurement of these values only happens during onScrollHandler, and so if the user is no longer scrolling, no re-measurement occurs and we enter the infinite loop.

The simplest way to force a measurement is just to fire a scroll event ourselves, but this may not be the fix we want. We might want to let useScroll handle observation of it's height, but this would require a larger refactor. Let me know if that's the route we'd rather go and I'll make the changes.

Another solution that might be a happy medium is for useScroll to return a function that can force a re-measurement. This might be the most flexible solution, because it would allow for measurements to happen for whatever reason we want 🤔

Update: I've made the refactor to return a force-measurement function, I think I like this better, but let me know what you think! If we'd rather force the measurement by just firing a scroll event, we can revert 87d6757

Additional context

---

🤖 Generated by Copilot at e44a129

Fix initial load bug in useInfiniteScroll hook. Dispatch scroll event on observed element to trigger fetch function.

🤖 Generated by Copilot at e44a129

• Dispatch scroll event on observed element to trigger initial data load (link)

[antfu]

Maybe we could put this at the beginning of checkAndLoad? Here I think it's better to do after nextTick

[scottbedard]

Good call, I like that better! Resolved 0ef4e25