fix: Respect markAsReadOnScroll setting

[NikolaM-Dev]

Problem

When markAsReadOnScroll is disabled, articles were still being incorrectly marked as read when users jumped through the chat using the j and k keyboard shortcuts. The jump navigation was bypassing the setting check.

Solution

Added validation in the useHotkeys hook to respect the markAsReadOnScroll setting during keyboard jump navigation. Now when users press j or k, we check the setting before marking articles as read—consistent with scroll behavior.

Changes Made

• useHotkeys hook: Added check for markAsReadOnScroll before marking messages as read on j/k jumps

Testing

• Disabled markAsReadOnScroll, used j/k to jump—articles no longer auto-mark as read
• Enabled markAsReadOnScroll, verified j/k jumps also mark as read (expected behavior)

[electh]

Thanks for the detailed report.

This behavior is actually by design. When navigating with the j/k keyboard shortcuts, the app assumes that jumping to an article indicates you have intentionally viewed it, so the item is marked as read regardless of the markAsReadOnScroll setting. The scroll-based setting only governs automatic read marking during passive scrolling.

[NikolaM-Dev]

This behavior is actually by design...

Ohh, that makes sense, thanks for clarifying! And kudos to you for the thoughtful UX here. I actually really appreciate having that level of control, so this works perfectly for my use case. No issue at all on my end 👍