LNReader/lnreader-plugins

Duplicate Results and Loading Animation Glitch

Opened this issue · 1 comments

Pheonix-Flames commented

Steps to reproduce

  1. Open the LNReader app and navigate to a novel source.
  2. Perform a search within the source to generate results.
  3. Scroll down until you encounter the loading animation.
  4. Stop scrolling before reaching the end of the page to keep the loading animation visible.
  5. Wait for an extended period to observe that the subsequent content does not update.
  6. Scroll all the way down to the end of the loading animation.
  7. After the loading animation completes, scroll back up to the top.
  8. Notice that a duplicate set of results appears, indicating the problem of duplicating previous novels.

Expected behavior

When searching for novels, the app should display results promptly without delay. As users scroll down, any loading animations should vanish once new content is fully loaded. This ensures that subsequent content updates smoothly, without duplicating previously listed novels.

Actual behavior

When users search for novels within a source and scroll down, they encounter a loading animation. However, this animation persists even after waiting for an extended period, and the subsequent content does not update until users scroll all the way down to the end of the loading animation. This leads to a duplication of previously listed novels, creating a glitch in the browsing experience.

Record_2024-05-03-14-59-13_20a0a7b89aa33ffd9ff252f469dd0447.mp4

LNReader version

2.0.0

Android version

Android 11

Device

Realme 3 Pro

Other details

No response

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
  • I have written a short but informative title.
  • If this is an issue with a source, I should be opening an issue in the sources repository.
  • I have updated the app to version 2.0.0.
  • I will fill out all of the requested information in this form.
nyagami commented

This is plugin issue, this plugin search function doesnt check the page number.
You should provide plugin information