joelacus
Mark posts as red button disappears after clicking
The new mark as read button works great in 2.3.1, thanks.
When I click the expando on an image/video post, the mark as read checkmarks disappear. Or when I click the mark as read checkmark on a link post, it then disappears. By itself that would be great and I would appreciate it. However, when I re-load the page, all the buttons come back even though the links stay marked as read.
It would be nice if they stayed gone after re-load if the associated link is read. Or if that's difficult, then just don't have them disappear at all. The in between makes the page inconsistent.
This really isn't a big deal, but I figured I'd report it. If you don't think it's worth fixing that's totally fine and I'll live with it. Having them at all is great.
We can’t do much about it, this is a browser limitation imposed on the extension’s background script and History API, which we use to mark posts as visited (if you want to read some technical details refer back to #201 or f703dc5). @joelacus can probably decide whether to keep the behaviour of removing the read mark, but I've experienced significant function slowdowns when RE checks the visited state of each post (see #203).
On 14 Oct 2025, at 08:17, Watchful1 @.***> wrote:
Watchful1 created an issue (joelacus/RedditEnhancer#206) image.png (view on web) The new mark as read button works great in 2.3.1, thanks. When I click the expando on an image/video post, the mark as read checkmarks disappear. Or when I click the mark as read checkmark on a link post, it then disappears. By itself that would be great and I would appreciate it. However, when I re-load the page, all the buttons come back even though the links stay marked as read. It would be nice if they stayed gone after re-load if the associated link is read. Or if that's difficult, then just don't have them disappear at all. The in between makes the page inconsistent. This really isn't a big deal, but I figured I'd report it. If you don't think it's worth fixing that's totally fine and I'll live with it. Having them at all is great. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
The original behaviour is that once you click the "mark as read" button, you don't need to click it again so it disappears. It would then check each post when you load a feed to see if you have the post URL in your browser history and not show the button again if it is. This worked great for me, but apparently it caused significant slow down for other people, so I removed this check to keep it stable for everyone. I was concerned though that this might cause UX issues, and it seems it has. I could reintroduce this check so they won't show again, but with an option to toggle it off if it causes any issues.
That sounds great. Could you then make the toggle off for this cause the buttons to not disappear at all?