Sharkey/packages
dakkar dbfafe25e3 rework pagination - fixes #491
previously, when adding items either at the beginnig (e.g. new notes
coming in while we're not looking at the top of the timeline) or a the
end (e.g. more items arriving from a background fetch) of a paginated
view, the resulting list got truncated to `displayLimit`, potentially
throwing data away and causing a new fetch.

This, coupled with the async nature of scrolling & fetching, could
cause weird results.

Also, `offset` was always incremented by the size of the fetched
results, even if not all of them were displayed, meant that it was
possible for offset-based pagination to drop items.

Finally, the "queue" of new items (usually, new notes) also got
truncated to `displayLimit`, which again could drop items (this effect
was usually masked by the first point: when scrolling to the top of
the timeline, if the queue's length was equal to `displayLimit`, those
notes displaced any existing ones, `unshiftItems` set
`more.value=true`, you got scrolled to the top, and notes were fetched
again, so you lost your position but at least all notes got shown,
eventually)
2024-04-19 13:35:18 +01:00
..
backend merge: hide images/videos in og cards, when under a CW - fixes #487 (!488) 2024-04-11 20:40:38 +00:00
frontend rework pagination - fixes #491 2024-04-19 13:35:18 +01:00
megalodon fix: send null for empty edited_at in mastodon api 2024-04-04 10:43:28 +02:00
misskey-bubble-game merge upstream for 2024.2.1 2024-03-02 16:36:49 +00:00
misskey-js merge upstream for 2024.2.1 2024-03-02 16:36:49 +00:00
misskey-reversi merge upstream for 2024.2.1 2024-03-02 16:36:49 +00:00
shared chore: use @misskey-dev/eslint-plugin (#12860) 2023-12-31 15:26:57 +09:00
sw merge upstream for 2024.2.1 2024-03-02 16:36:49 +00:00
meta.json refactoring 2021-11-12 02:02:25 +09:00