in reply to Re^3: Ability to mark specific "newest nodes" nodes as read
in thread Ability to mark specific "newest nodes" nodes as read

One thing not mentioned yet is that HTML offers this since the earliest days, and already visited links have at least another color.

The effect is subtle², since I'm a bit color blind, but I'm pretty sure one just needs to adjust the CSS settings⁴ for "visited" (?) to change colors or other attributes.

Dunno the right CSS code for that, but other monks and search engines might help.¹

Disclaimer: this won't help if you use multiple browsers tho.³

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery

Edits/Updates
¹) "visited" it is: https://developer.mozilla.org/en-US/docs/Web/CSS/:visited

²) and probably watered down by color settings for different creation dates.

³) and you'll have to open each post individually for them to be "visited"

⁴) in Display Settings or RAT Style Settings . Additionally Newest Nodes Settings might be of interest too.

  • Comment on Re^4: Ability to mark specific "newest nodes" nodes as read (CSS :visited)

Replies are listed 'Best First'.
Re^5: Ability to mark specific "newest nodes" nodes as read (CSS :visited)
by Danny (Chaplain) on Mar 05, 2024 at 17:30 UTC
    "and already visited links have at least another color"
    Yeah, that's what I've been using. I just click any read node directly to mark it as visited. I guess one setting that would be nice for both Newest Nodes and Recent Threads would be the ability say "I've checked all older than [x] days old" instead of simply "I've checked all of these". I realize you can "Clear my 'last checked' time" and simply set 'Show nodes created within the past x days', but then you lose the td.reply-new css styling functionality.
[reply]
      > would be nice for both Newest Nodes and Recent Threads would be the ability say "I've checked all older than x days old" instead of simply "I've checked all of these".

      OK, I see what you mean now.

      I don't know if the gods would approve that and I learned not to invest in patches which will not be accepted.

      But you can hack that for yourself.

      If you right-click on [I've checked all of these] you'll be offered to investigate the button in the dev-console.

      There you'll find a timestamp in pageloadtime which can be manipulated

      <form method="post" action="?" enctype="multipart/form-data">
<span><input type="hidden" name="node_id" value="3628"></span>
<input type="hidden" name="pageloadtime" value="1709739362">
<input type="submit" name="viewedNewNodes" value="I've checked all of 
+these">
</form>

      [download]

      after substracting 86400*days I filled the new value in and hit the button.

      To make it more comfortable, you can either write a bookmarklet with javascript: protocol or a nodelet-hack to do so.

      HTH! :)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery

[reply]
[d/l]
[select]
      > but then you lose the td.reply-new css styling functionality.

      Not sure what you mean...

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery

[reply]
        After you click "I've checked all of these" nodes created after that time will contain the tags td.reply-new and td.reply-new-body which can be used to style newly created nodes. For example, you can use a different background color to highlight new nodes within a thread. After you click "Clear my 'last checked' time" these tags no longer appear.
[reply]

In Section Perl Monks Discussion