3 ms·
I like :visited. It’s useful. I don’t want browsers to disable it, but developers to stop clobbering and disabling it on their sites. Any site I make will have
by chrismorgan 5y ago
I like :visited. It’s useful. I don’t want browsers to disable it, but developers to stop clobbering and disabling it on their sites.
Any site I make will have sane blue underlined links and purple underlined visited links. I’m willing to vary the shades of blue and purple, and I prefer to reduce the opacity of the underline when not interacting with the link, but I say general links should be blue and purple and underlined, and anything else is troublemaking.
(In https://github.com/w3c/csswg-drafts/issues/3012 https://github.com/w3c/csswg-drafts/issues/3012, there’s talk of changing :visited to essentially work from the site’s perspective—exposing only history that the site could have tracked itself—rather than for the user as global visitedness does. This makes me sad, though I quite understand the perspective; to me, :visited has always been about the user, even though such first-party link following is its primary use.)
- gowld 5y agoThe think you like is client link styling, not :visited attribute manipulated via CSS/JS.
- magicalist 5y agoNot sure what you mean. Under that proposal :visited wouldn't be available for styling or scripting except for links the site could already know that you visited.