Problem: On occasions, an edit is made that appears to be good faith, but I want to check it more thoroughly, either when I have more time or better access to sources. However as diffs are automatically marked as visited when I view them, it is not currently possible to keep it flagged to remind me to review it later.
Proposed solution: When a diff is viewed on a page that is in a watchlist, allow a method of marking the diff as unvisited/unread.
Why do you need to care if the diff is or is not visited if the diff to be consumed is on another tab (or window, however you want to organize things)? Izno (talk) 19:24, 17 January 2022 (UTC)Reply[reply]
Because it may be some time before I can properly review the diff (e.g. I'm away from home, and I don't have access to a reference book), and I don't want to fill my browser with open tabs for that period of time. No different to marking an email as unread if it needs further action later. Voice of Clam (talk) 19:47, 17 January 2022 (UTC)Reply[reply]
The difference is that this is a team made to resolve volunteer wishes and Outlook/Gmail are not. ;) I definitely know what my priority will be when we get to voting if it's an issue for you of "I don't want to have tabs open". Izno (talk) 06:32, 18 January 2022 (UTC)Reply[reply]
Yes, doing that is part of the reason I have hundreds of open tabs everywhere. ~~~~ User:1234qwer1234qwer4 (talk) 23:22, 11 February 2022 (UTC)Reply[reply]
Are you talking about the watchlist's last visit timestamp feature (ie. bolding)? The browser's CSS styling for visited links? Patrolling? Something else? --Tgr (talk) 00:32, 30 January 2022 (UTC)Reply[reply]
Seems reasonably helpful, though maybe less so for people using email watchlist notifications, which can be marked as unread. ~~~~ User:1234qwer1234qwer4 (talk) 23:24, 11 February 2022 (UTC)Reply[reply]
Support An article/diff becoming "visited" and the resulting removal of the alert that the edit triggered are among the few non-reversible actions one can take. DMacks (talk) 22:16, 28 January 2022 (UTC)Reply[reply]