Paging issues with dynamic state change for suggestions

[fricklerhandwerk]

Switching to the next page after dismissing suggestions with JS enabled will skip items in the previous page.

Reproducer

1. Load first page in suggestion view

• Open second page in new tab, take note what's the first item

2. select/dismiss a few items
3. Switch to second page

The first item on the second page will be different than what it was previously. As a result, users will miss what has shifted to the front.

With dynamic loading it's now more involved to reason about paging, and we'll have to come up with a pattern that scales and allows for both good UX with JS enabled but also degrades nicely with acceptable performance.

[fricklerhandwerk]

Since we can do arbitrary dynamic stuff in this realm, how about we trigger shifting an element in from the next page once we remove one on the current (and vice versa)? This has the additional advantage of being much more performance tolerant, so we have time to reshuffle the paging in the background.