On one of the NodeBB communites I'm active on, I've blocked a user with the personal Block User option. After that block, I've had a pretty poor experience with entering threads through clicking on a notification and also with the auto-refresh after adding a post to a thread.

Our forum's current NodeBB version is: 1.14.3

• When clicking on a notification (e.g. for upvotes or a reply/mention), I often get thrown into the thread with the post being notified for not even in the viewport, and the post referenced by the notification is not showing as highlighted by the time I find it.
• When auto-refreshing after posting to the thread, instead of the auto-refresh scrolling to the post I just made like I expect, I'm thrown back several posts, often to the point where even the post I was replying to doesn't appear on screen.
• I'm experiencing similar problems both in desktop mode (Windows 10 / Chrome latest stable) and on mobile (iOS / Safari)

I suspect that most of the times I'm having problems, the blocked poster is the most current poster in the thread at the time I click the notification / post a reply (he's a very prolific poster), but I haven't really experimented with turning block on/off to verify that.

I've also noticed that there's some weirdness in thread sorting as a result of the block (thread sorting on /recent, which is my default view, seems to sort based on the time of the actual last post, not the time of the last post I can "see"), but I can imagine that's probably more effort to fix than the value would justify.

Oh. Yeah, the current behavior is super unintuitive to me.

It would make much more sense to me if it kept its current copy and how it builds the list -- "here are topics that have recent activity" -- but if, instead of always going to post #1 in the linked topic, it went to your last unread position automatically. It was very frustrating to keep coming back and trying to click into the Scrolling test thread while I was interacting with it, and keep getting shunted back to post #1.

I guess that makes this more of a feature request than a bug report, if the "go to post 1 in the recent topics" behavior is intended.

@PitaJ

Then can the copy be updated to reflect that it's recent posts? And I would expect that if it's recent posts, it should take me to the very last post in the thread, not the very first post in the thread.

When I click on a topic in the "Recent Topics" header, I get sent to the first post of that topic, and get a toaster option to return to my last read position.

I expected the behavior to match the topic list, where I get sent to my last read position directly.

Browser: Chrome 58 latest on Windows 10

Much thanks, our admin just pulled the update and the settings page looks much better now.

@julian As per your request, here's the ping. Judging by the comments in the thread that popped up for this on our forums, the consensus is pretty heavily toward not defaulting to on for the notification sounds.

My home forum, The Daily WTF, just recently pulled the updates for notification sounds. One thing that bothered me about the default behavior of those sounds was that they're on by default, but the profile page (in Chrome latest on Windows 10, at least) defaults to blank values in the sound drop down boxes, so it makes it very difficult to determine what the right method for disabling the sounds is.

I would like to see one of the following changes made to the notification sounds settings (in decreasing order of preference):

1. Default to sounds off, especially on an upgrade for existing users
2. Add a checkbox next to each sound option in the Notification & Sounds setting to indicate whether the sounds are enabled or not. Or, at least put in a "disable all sounds" (or "enable sounds") checkbox that controls sounds globally.
3. Fix the profile page so that the notifications & sounds section actually shows a selected sound when you first navigate after the default settings are applied. Preferably also change the blank option (that disables the sound) so that it shows text like "Sound disabled".