Open KitsuneRal opened 2 years ago
Some work has been done in 775245d9; that makes for somewhat confusing UX where the same button forces loading chunks of history and then jumps to the read marker. A better way (barring discontinuous timeline) would still be to load as much history as needed providing some feedback on what's happening and then automatically navigate to the read marker.
To reproduce:
An expected result (that's how Element iOS works, e.g.) is to load history until the event with the read marker is encountered and then navigate to it. It can be somewhat slow due to network requests (potentially several) so visual feedback is also important. Note: loading history until the read marker sounds like a good addition to libQuotient.