Delayed "mark as read"?

(Ed Ball) #1

More than once, I’ve clicked on a post on the Unread page, gone back to the Unread page, even refreshed the Unread page, but still the post remains unread, even through many different unread posts. Is this likely a bug, or just an expected result of caching or “eventual consistency” or something?

Sorry I can’t reproduce consistently; if it is likely a bug, I’ll let you know if I figure out how to repro.

(Jay) #2

I think this is a bug too. It also affects the “new-posts” number next to topics which stays showing that there are new posts in a topic even when there are not.

(Ian Carroll) #3

How long were you on the post thread? Discourse might actually be doing this on purpose so you’ll read the thread.

(Jeff Atwood) #4

It is possible to trigger this if you click the back button immediately after loading the topic, e.g. you don’t actually “read” the posts on the page.

It intentionally takes a bit of time for the JavaScript on the page to acknowledge read of posts, since nobody can read infinitely fast, etc.

(Ed Ball) #5

I’ll have to keep that in mind the next time I encounter the bug. Maybe I had already seen the post in an email and left too quickly for Discourse to mark it as read…

(Jay) #6

I thought it went by when you scroll-down? For me, the red bookmark moved down to the last post but the topic list still showed [1] unread post - I guess it means the last post itself wasn’t read for long enough? Maybe the length should be a function of the post-length/char-count?

(Jay) #7

Though I’m not sure about this - it’s happening for me right now on this very topic. Even though my own post is the last one (of course I’ve read it) the “unread” list still shows this post.

I don’t know if this idea fits with the UI ethos but there could be a vertical progress bar to the right of the posts, that drains down line-by-line (so the height of the box would define the read-time) to a “Read √” button at the bottom - clicking it marks as read immediately. Actually I hate this idea, but it’s frustrating when some internal mechanism is misbehaving and there’s no visual feedback :slight_smile:

(Jeff Atwood) #8

What web browser are you using? There’s a normalize job that runs every 24 hours so it should not be permanent. Not seeing this a lot myself, but it can happen.

(Jay) #9

You mean there’s no admin feature for seeing user-agents of users? :slight_smile:
I’m in Firefox 20.0 on a Mac - btw, good job to whoever insisted on retina-display support - even for profile images, crisp!

(Brentley Jones) #10

This is the same bugs I reported a while ago.

The first one describes a case where the page itself won’t allow you to read it all. The second 2 mirror what is being described in this topic. Below are some other people reporting the same bug.

Yes, there is a job that covers it up but it would be nice to fix it as well :wink:

(Ian Carroll) #11

Why isn’t that job run every 12 hours, or even 6? There should be some control over this, and I think that the job would be more helpful if run more frequently.

(Jeff Atwood) #12

Let us know if you’re still seeing this.

(Jeff Atwood) #13