No "infinite" scrolling on "unread" section

ClassicGMR

I am also still experiencing this. Has been a few weeks (I think).

Windows 10 Home
Firefox 64.0 (updated and cache cleared)
Internet Explorer 11.471.17134 (which I NEVER use - just tested it)

EctoOne

Same here, I noticed that yesterday because I had a notification for a thread that wasn't in the recent list.

BuZz

@EctoOne and it's still happening now for you? Might be worth waiting as it could be an issue that resolves as new replies are made. (Forum was updated today).

EctoOne

@BuZz it is. But it is really weird. I had 27 unread posts, it showed 21. When I right clicked on a link to open it in a new tab, it loaded a new entry.

Oh, it only showed 20 entries at first, then 1 was added when reaching the end. I tried scrolling up and down, because that worked for me before, but nothing else happened.

hiulit

@BuZz Still happening to me. The notification says I have "77 unread topics" but I only see 21 and I can't scroll to see the others.
It only happens in the "unread" section. The other sections work fine.

BuZz

@hiulit it's possible that they did fix it but it won't help old topics. So I'll check in a week.

EctoOne

@BuZz Any news on this? I just noticed that the list still only shows 20 entries.

BuZz

@EctoOne no. The fix that was backported to this version doesn't seem to work. I'm inclined to wait for v 1.12 and if it's still broken I'll open a ticket with NodeBB.

BuZz

I have now reported this issue upstream - https://github.com/NodeBB/NodeBB/issues/7209

ClassicGMR

Awesome! :) It sucks to not have that feature working.

BuZz

As a workaround for this, if you go to your user settings and switch to paginated mode, you can view all unread topics. It's only broken in infinite scroll mode.

cyperghost

@BuZz
Yes true, that works fine - unfortunately this also affects the scrollmode inside an opened thread, too.

Inside a thread the endless scroll works fine. In topic overview you are stuck to 20+1.
Well... time will pass and a fix will come ;)

BuZz

This is now fixed. Thanks to the NodeBB devs :-)

hiulit

@BuZz Yeah, it is! Alright!