Articles are automatically marked as down when clicking another feed

Tiny Tiny RSS Support
1
  • [ ] I’m using stock docker compose setup, unmodified.
  • [X] I’m using docker compose setup, with modifications (modified .yml files, third party plugins/themes, etc.) - if so, describe your modifications in your post. Before reporting, see if your issue can be reproduced on the unmodified setup.
  • [ ] I’m not using docker on my primary instance, but my issue can be reproduced on the aforementioned docker setup and/or official demo.

Installed plugins:

  • FeedMei
  • ttrss-plugin-googlereaderkeys

Here are the steps to reproduce this issue:

  1. Check Mark read on scroll on Preferences.
  2. On three panel view, click one feed on the left, then scroll down the article list until all articles are marked as read.
  3. Click another feed on the left. Since the article list has been scrolled down, all articles on another feed are marked as read automatically.

How to fix:

Navigating article list to the top before clicking another feed can avoid this issue.

  • Tiny Tiny RSS version (including git commit id): Tiny Tiny RSS v22.12-8ea5371
  • Platform (i.e. Linux distro, Docker, PHP, PostgreSQL, etc) versions: Debian 11
2

is this a third party theme or something? try logging in tt-rss safe mode.

3

There’s no issue on safe mode or changing to the default theme.
I’ll report this issue to the author of FeedMei. Thanks.

4

Link here: Articles are automatically marked as down when clicking another feed (feedmei+) · Issue #5 · ltGuillaume/FeedMei · GitHub

5

@fox

I’ve been looking into disabling smooth scrolling (which is (re)introduced by this theme) only if the feature Mark read on scroll is enabled. I haven’t been able to find anything when searching for catchup or scroll in the source, but just to be sure:

Is there a class set, or anything else done that’s accessible via a CSS selector that could help determine if Mark read on scroll is enabled?

Edit: Hmz I see you’ve been battling smooth scrolling a lot before getting rid of it entirely.

6

there probably isn’t but you can make a plugin which would set it during frontend load.