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

> > 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}

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

Replies are listed 'Best First'.
Re^11: Ability to mark specific "newest nodes" nodes as read (POC td.reply-new combined with :visited ) by LanX (Saint) on Mar 06, 2024 at 17:42 UTC
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]
Re^12: Ability to mark specific "newest nodes" nodes as read (POC td.reply-new combined with :visited ) by jdporter (Paladin) on Mar 07, 2024 at 13:03 UTC
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]
Re^13: Ability to mark specific "newest nodes" nodes as read (POC td.reply-new combined with :visited ) by LanX (Saint) on Mar 07, 2024 at 14:12 UTC
To avoid misunderstandings, did you try it? The fact that they are orthogonal means they can be combined to signal different states. Orthogonal doesn't mean exclusive. FWIW: I'm thinking about ways to apply it to my RAT view, (alas traffic is so low that it might not worth it ;) Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]