in reply to Re^8: Ability to mark specific "newest nodes" nodes as read (CSS td.reply-new)
in thread Ability to mark specific "newest nodes" nodes as read

Still have to check how this plays combined with the aforementioned :visited pseudo class

It won't meaningfully. The :visited status of a link is managed by the browser, and it only pertains to links you have clicked. PerlMonks knows whether it has shown you any given post/comment, even when you didn't visit it directly by clicking on a link. Where I find :visited useful is when I do a SuperSearch and get a list of results. I can easily see which hits I may have already clicked on recently.

  • Comment on Re^9: Ability to mark specific "newest nodes" nodes as read (CSS td.reply-new)

Replies are listed 'Best First'.
Re^10: Ability to mark specific "newest nodes" nodes as read (CSS td.reply-new)
by LanX (Saint) on Mar 06, 2024 at 16:01 UTC
    > > Still have to check how this plays combined with the aforementioned :visited pseudo class

    > It won't meaningfully.

    Not sure about that, one should be capable to supersede it with :visited to neutralize the effect.

    EDIT: Of course only within the current browsers scope.

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

[reply]
[d/l]

      Something like this works for me 

        
td.reply-new :link    { background-color: #F88 }
td.reply-new :visited    { background-color: #FFF }

      [download]

      It's only a rough demo, but meaningful enough IMHO.

      YMMV! :)

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

[reply]
[d/l]

        I didn't say that :visited was not useful. I was saying that coloring/distinguishing unread thread comments does not meaningfully "play combined with :visited". They're almost entirely orthogonal.

[reply]

In Section Perl Monks Discussion