The potential partial response wasn't handled properly which resulted in apollo not updating the cache for the successful part.
E.g., chapter reload failed, and manga refresh succeeded. The manga data of the response should have updated the manga in the cache.
The native language code returned by the browser could be a code that is not included in the defined ISOLanguages object. E.g. "en-GB" while the object only has "en".
This caused the "English" browse language to not be able to get selected as an allowed language.
* show only the last chapter red
* fix : case when a load has not enough different manga
* fix : problems with the load of chapters
* Fix "filteredOutAllItemsOfFetchedPage" determination
* Remove logic to load until scrollbar appears
`Virtuoso` (list) doesn't have the same issue as `GridVirtuoso`, i.e. `endReached` gets called on initial render in case there weren't enough items
* Increase history page size (50 -> 150)
Due to the new filtering, it can take forever to load the initial pages/next pages
* Use lodash "uniqBy" for filtering
* Update changelog
---------
Co-authored-by: schroda <50052685+schroda@users.noreply.github.com>
With 4f4ca98290 the chapter queries are getting evicted to trigger a refetch. This caused the reader to enter the loading state, which messed up the current reading position.
When resuming a migration search, it was possible that an entry search was partially done.
In this case, when retrying, the sources with search results were not retried.
If all retried source searches failed, it was incorrectly treated as if all source searches failed, since it only considers the actually executed search sources, which only included failed/pending sources.
Observers got disconnected and started again.
Since the images have already been rendered at this point of time, the mutation observer on the scroll element does not detect them anymore.
Thus, exiting image resizes were not observed anymore and did not trigger the preservation logic
This was only was noticeable in case the transition page was disabled.
Due to potential layout shifts and scrolling the initial page into view, the infinite chapter logic got triggered and loaded the previous chapter.
This is not a 100% guarantee that it won't happen, slow devices might still run into this issue
