You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been experiencing issues with the web app's article loading system ever since the move to the new interface. It involves the way articles are loaded when you scroll down the articles list, and occurs on both tile and list views.
The first issue is that the system will become "locked" at exactly 50 articles shown. No new articles will be loaded by scrolling, nor will the "More Search Results" button be visible. This can happen even after loading more articles than that on that tab (eg. Subscriptions), with the app going back to 50 articles sometimes even after doing something in another program for a while without switching app tabs. To my knowledge no articles are skipped when this happens. Deleting/moving articles from this list of 50 will cause the list to shrink without replenishing itself from unloaded items.
The second issue I've only found to affect the Archive tab, but that may be due to that being the only tab I have enough articles in. Basically at around over 170 articles it will stop loading naturally and start only intermittently loading one article at a time. When this happens the "More Search Results" button is visible, but that disappears and the system stops completely only a few articles after. Comparing the loaded articles with the Android app's list shows that many articles start being skipped at the point where the loading system starts acting weird, and the last article loaded is not the last article in my Archive (which contains over 300 articles). The articles that are loaded one at a time are not bunched up together in the real list order. The skipped articles can be found on the web app using label searches, they just fail to load under high article counts in the Archive.
This issue was tested on Firefox only and does not seem to affect the Android app. Clearing the cache and logging back in will fix the first issue temporarily, but it will appear again with some use. The second issue does not get fixed at all. In addition, sometimes the first issue will override the second issue, meaning Archive gets stuck at 50 articles loaded too. While writing this it just happened again, although being stuck at 51 articles with the 50th article skipping to the "last" article loaded when the second issue is present. Both issues sometimes fix themselves, but I'm not sure what causes this (possibly related to not using Omnivore for a while) and the issues will soon pop up again
In addition there are several more minor issues I'd like to bring up. Let me know if I should submit them as separate issues
The folders on the web app do not remember their open/close states
The webpage icon still shows the non-yellow transparent one on bookmarks and history on Firefox. It is likely trying to retrieve it from https://omnivore.app/favicon.ico . The icon that shows when the web app is open in a tab is the yellow one as expected.
Labels removed (as in removed entirely, not from a specific article) on the web app do not disappear on the Android app
Feeds that have been removed are still present on Edit Shortcuts. Please give us the option to remove them.
Upon deleting/archiving an article on the web app, the article will still remain present on opening the Android app/the first refresh when new articles get added. It only updates upon refreshing the list again.
The scroll bar on the Android app when reading an article sometimes goes "invisible". I think it actually turns white against my white reading theme. Unsure what triggers this
The text was updated successfully, but these errors were encountered:
I have been experiencing issues with the web app's article loading system ever since the move to the new interface. It involves the way articles are loaded when you scroll down the articles list, and occurs on both tile and list views.
The first issue is that the system will become "locked" at exactly 50 articles shown. No new articles will be loaded by scrolling, nor will the "More Search Results" button be visible. This can happen even after loading more articles than that on that tab (eg. Subscriptions), with the app going back to 50 articles sometimes even after doing something in another program for a while without switching app tabs. To my knowledge no articles are skipped when this happens. Deleting/moving articles from this list of 50 will cause the list to shrink without replenishing itself from unloaded items.
The second issue I've only found to affect the Archive tab, but that may be due to that being the only tab I have enough articles in. Basically at around over 170 articles it will stop loading naturally and start only intermittently loading one article at a time. When this happens the "More Search Results" button is visible, but that disappears and the system stops completely only a few articles after. Comparing the loaded articles with the Android app's list shows that many articles start being skipped at the point where the loading system starts acting weird, and the last article loaded is not the last article in my Archive (which contains over 300 articles). The articles that are loaded one at a time are not bunched up together in the real list order. The skipped articles can be found on the web app using label searches, they just fail to load under high article counts in the Archive.
This issue was tested on Firefox only and does not seem to affect the Android app. Clearing the cache and logging back in will fix the first issue temporarily, but it will appear again with some use. The second issue does not get fixed at all. In addition, sometimes the first issue will override the second issue, meaning Archive gets stuck at 50 articles loaded too. While writing this it just happened again, although being stuck at 51 articles with the 50th article skipping to the "last" article loaded when the second issue is present. Both issues sometimes fix themselves, but I'm not sure what causes this (possibly related to not using Omnivore for a while) and the issues will soon pop up again
In addition there are several more minor issues I'd like to bring up. Let me know if I should submit them as separate issues
The text was updated successfully, but these errors were encountered: