I own a Single page application (web) displaying a list of items.
Each item represents an announcement, imagine for example some bids.
A user can list the current bids, and click on one of them in order to display the "show" page, showing the bids in detail.
How to handle the user navigation between different views of bid?
When he clicks on browser's back button (or an appropriate return button), I would expect the application to refresh the bids list, in case where title, or prices etc.. were updated, or even new bids added that would lead to sort again the list.
More precisely, should I adopt a pagination mechanism (splitting pages through numbers), or a scroll infinite mechanism?
The issue I notice with scroll infinite would be that it would be incompatible with bids list refresh.
Indeed, if my loading rule was to load 20 items per 20 items, if the user clicks on the 190th, a back leading to a refresh would only retrieve the first 20 items. User would still be forced to scroll until he finds the 191th item => sounds very bad, regarding UX.
On the other hand, a scroll is easily retainable when dealing with classical pagination mechanism, (like Ebay does for instance).
IMHO, Scroll infinite would be relevant if the list was not refreshed during this user's use case of navigation (since I could retain the current scroll position) or if the "bid detail" page would be opened in another window/tab of browser.
Am I wrong? What would be a good practice in this case?