Skip to content
This repository has been archived by the owner on Jun 4, 2020. It is now read-only.

"Mark all as read" marks unseen articles as "Read" #156

Closed
skoontastic opened this issue May 23, 2013 · 12 comments
Closed

"Mark all as read" marks unseen articles as "Read" #156

skoontastic opened this issue May 23, 2013 · 12 comments

Comments

@skoontastic
Copy link

I searched through the issues, but didn't see anything about this.

Expected behavior: Clicking "Mark all as read" should mark only the unread visible articles as read. Not articles that haven't been viewed.

Actual behavior: Clicking "Mark all as read" marks articles as read that have (seemingly) been refreshed in the background.

So, I have a list of feed articles up that are not read. I read through them, click "Mark all as read", then check back on the "Read" items and find articles that I never saw. For instance, just now I read through articles and the last article was from 8:00. I clicked "Mark all as read" and checked the "Read" items to find several articles in there from 8:00 - 9:00 that I never saw. Is there any way to change this behavior?

I have tried to click Unread first before clicking "Mark all as read" to refresh, but then I get a weird behavior where some feed items from earlier in the day, that I have never seen, pop in and I have to read through the whole list of Unread items to find those.

@Zegnat
Copy link
Contributor

Zegnat commented May 23, 2013

👍

I agree ‘Mark all as read’ should only mark those that are currently being displayed as unread an no others.

This behaviour should get slightly less annoying if #18 lands and the entry list is refreshed automatically. But even then there might be moments where unseen items get unexpectedly marked as read. I currently just do a forced browser refresh before I hit the button but this shouldn’t be needed.

@joschug
Copy link

joschug commented May 30, 2013

I tend to disagree. "Mark all as read" should to exactly that. And actually I'm quite glad that it does, after importing ~180 feeds and having to clear our about ~10.000 unread items that I've actually already seen.

But I don't see why this couldn't be made user-configurable. Just add a toggle to the settings that gives the user a choice of the desired behavior.

I'd opt for one exception though: Articles that have been explicitly marked as "unread" should be excluded from the action of this button.

@Zegnat
Copy link
Contributor

Zegnat commented May 30, 2013

The point here is to mark all as read up to the last item that has been loaded into the browser, to make sure you are not missing anything after pressing the button. How will this stop you from clearing out items after an import?

With unseen it doesn’t mean entries you haven’t looked at, it means entries that have never been sent to your browser because you haven’t done a refresh yet.

@joschug
Copy link

joschug commented May 30, 2013

Ok, then I misunderstood what you meant by "unseen". To me, that sounded like only the articles currently visible on the screen.

@wlgreg
Copy link

wlgreg commented Jun 4, 2013

Add my vote for implementing this. "Mark all as read" should not touch any articles that haven't been loaded in the browser. If I've loaded and am working my way through 300 articles, and 50 come in while I'm reading, "Mark all as read" should only affect the original 300.

@dahanbn
Copy link

dahanbn commented Aug 11, 2013

+1 Mark all as read should not affect possible new items that got fetched during reading the already fetched items.

@skoontastic
Copy link
Author

Just bumping this thread, as it's been a few months since I posted it.

After wandering around looking for a good desktop RSS reader that syncs with FeedBin, and finding nothing good, I thought I would try the web app again. There have been some awesome improvements, but this issue still remains. When I click "Mark All as Read", it will mark items that have been collected in the background as read.

Example: While I was reading an article, I received a push notification that a new article was received. The article didn't show up in the article list, and the web app didn't show me that anything new had come in. So, for fun, I click "Mark All as Read", and, sure enough, it had marked the article that I hadn't read yet as "read".

Google Reader used to hold the messages that were not visible yet, and then display them as unread when I would click "Mark all as read".

@dahanbn
Copy link

dahanbn commented Jan 16, 2014

Please reopen that issue. I support the message above. To change that behaviour would be a great improvement of the web app.

@benubois
Copy link
Member

I've made an attempt at resolving this. I've never actually run into this in day to day use of Feedbin, but I do see how it could happen.

@skoontastic
Copy link
Author

I just did a Mark all as Read, and boom, a new article was waiting and not marked as read. I also checked and, so far, nothing has been missing today.

Wonderful! Thank you!

@skoontastic
Copy link
Author

I can confirm now that this is definitely working. I marked all as read, and had two new unread messages waiting. Perfect! Feedbin is now definitely my go-to RSS reader.

@benubois
Copy link
Member

@skoontastic excellent. Thanks for testing this out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants