Add more Infinite Scroll jQuery events

[ste93cry]

Following request @georgestephanis in issue #1488, I'm opening this ticket to request the post-load event in the Infinite Scroll jQuery plugin to be namespaced. It would be useful to add also some more extension points, for example a pre-load event or something that allows the editing of the query_args from client side before sending the AJAX request. As event data it would be useful to have access to the Scroller instance, to edit it's internal variables if needed (like the page number).

[georgestephanis]

Anyone know if we have third party integrations to the existing event already that namespacing would break?

[jeherve]

We've advertised post-load on the support page since the beginning, so there might indeed be quite a few people using it in personal projects out there: http://jetpack.me/support/infinite-scroll/#js-events

[ste93cry]

For fallback support, you could mark as deprecated that event and trigger it twice, one time as before and another time under the appropriate namespace that new events should use too. Then, in a major new version you remove the old trigger. This means that the plugin won't break immediatly the compatibility and users will have time to upgrade their scripts in order to use the new feature

[georgestephanis]

I really don't like the idea of breaking backward compatibility without actual cause (not just 'best practices' but the current pattern actually breaking things sufficiently to justify breaking other things while fixing it)

[ste93cry]

This is why I suggested to trigger the event twice, before the deprecated event is removed in a major new version.

[stale[bot]]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[github-actions[bot]]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.