Clicking a thread takes you to the most recently read post
-
Clicking a thread title takes you to the most recently read post, not the least recent unread post.
The difference doesn't matter much if you use infiniscroll (but you should be ashamed of yourself), but for those of us with pages, it means that clicking a thread title often takes us to the end of the last page we've read, with nothing new to see.
More than few times I've thought, "huh, nothing new to read" and clicked . When I do notice that there's a new page available, my reaction is more like " why does it delete two characters when I hit backspace onceI need two clicks instead of one to continue reading?"It's minor but it's irritating.
-
@error said in Clicking a thread takes you to the most recently read post:
It's minor but it's irritating.
It's also permanent, because this has been mentioned so many fucking times, and is such a simple fucking fix, but nothing's been done about it.
-
-
@error said in Clicking a thread takes you to the most recently read post:
if you use infiniscroll (but you should be ashamed of yourself)
Meh...clicking on "Next page" sounds like work.
But yes, they seem to want to go to the last read "for context" IIRC. Isn't the auto-navigate a local customization, @ben_lubar? Maybe we could have it navigate to
+1
?
-
@boomzilla said in Clicking a thread takes you to the most recently read post:
But yes, they seem to want to go to the last read "for context" IIRC.
I wouldn't be opposed to 1 post overlap between pages "for context", but that sounds like it might be more challenging.
-
@boomzilla said in Clicking a thread takes you to the most recently read post:
Isn't the auto-navigate a local customization, @ben_lubar?
-
@error said in Clicking a thread takes you to the most recently read post:
but that sounds like it might be more challenging.
It wouldn't be too bad - just set the LIMIT on the query to 1 more than you're multiplying the page number by to get the OFFSET.
It might be confusing to some users to see the same post twice, though.
-
@ben_lubar Hmm...weird. I guess not all themes use it then? My guess there was based on getting the toaster at c.nodebb instead of just going to the post.
-
@ben_lubar said in Clicking a thread takes you to the most recently read post:
It might be confusing to some users to see the same post twice, though.
It would definitely trigger rants from those types of users.
-
@boomzilla said in Clicking a thread takes you to the most recently read post:
@ben_lubar said in Clicking a thread takes you to the most recently read post:
It might be confusing to some users to see the same post twice, though.
It would definitely trigger rants from those types of users.
Add a "number of overlapping posts" to the pages plugin, default it to 0?
-
@error said in Clicking a thread takes you to the most recently read post:
pages plugin
Pages are a core feature.
-
I've noticed this too, and it's slightly annoying, but more annoying is the fact that the thread's unread bookmark is wrong after a jeffing.
I'd prefer getting the thread unread bookmarks to point to UIDs so that jeffing posts won't result in the thread's unread bookmark sending me directly to the end of the thread. And if it's no longer in the current thread, the unread bookmark should send me to the last post in the thread that was posted before the bookmarked post.
(That's for a thread's unread bookmark, which isn't actually a "bookmark". Actual bookmarks should be bookmarked by UID and they should follow the post even if it's moved.)
-
@anotherusername said in Clicking a thread takes you to the most recently read post:
I'd prefer getting the thread unread bookmarks to point to UIDs so that jeffing posts won't result in the thread's unread bookmark sending me directly to the end of the thread.
That was fixed a long time ago. Not to point to pids, but to update bookmarks based on jeff'd posts.
Unless you mess with the post sorting.
-
@boomzilla said in Clicking a thread takes you to the most recently read post:
Not to point to pids, but to update bookmarks based on jeff'd posts.
How's that supposed to work? When I jeff a thread (and thus have read all of it), the whole new thread comes across unread and I have to scroll to the bottom still. I just did it the other day when I jeff'd the flirting adventures thread.
-
@Yamikuronue Oh, I was talking about the thread where the posts were jeff'd from. Nothing is done to the target, though I guess that would make sense.
-
@boomzilla Are we sure it works?
The latest was the bad ideas thread... yesterday I noticed that my unread bookmark (the value in
ajaxify.data.bookmark
) was ~60 posts more than the number of posts that were in the thread. I just forced it down today by running:// e contains the post number to bookmark socket.emit('topics.bookmark', { tid: ajaxify.data.tid, index: e }, function(t) { if (t) console.error(t.message); else ajaxify.data.bookmark = e });
Unless maybe my unread bookmark has always been way beyond the end of that thread since way back when the bug existed, and I've just never really noticed that until yesterday.
-
@anotherusername said in Clicking a thread takes you to the most recently read post:
Are we sure it works?
Eh...it worked when I wrote it. I even added tests!
@anotherusername said in Clicking a thread takes you to the most recently read post:
Unless maybe my unread bookmark has always been way beyond the end of that thread since way back when the bug existed, and I've just never really noticed that until yesterday.
That's possible. I remember being way ahead in the status thread before it was fixed.
-
@boomzilla if I found another thread where my bookmark is way off, would there be any way for you to easily tell how recently that particular thread's undergone a jeffing?
-
@anotherusername I don't think so.
-
@boomzilla ok... well, in the meantime I've got this...