258
submitted 1 week ago by [email protected] to c/[email protected]
top 16 comments
sorted by: hot top new old
[-] [email protected] 50 points 1 week ago
[-] [email protected] 30 points 1 week ago

For a long time this protection was so strict in firefox that even the dev tools was not allowed to see the :visited styles.

[-] [email protected] 15 points 1 week ago* (last edited 1 week ago)

I hate that, in the modern web, customizing is so important that websites want access to the link itself, instead of just stylizing the div outside like normal.

[-] [email protected] 11 points 1 week ago

I'm not sure I understand the point you're making?

[-] [email protected] 5 points 1 week ago

That I don't want any website customizing the color, font etc. of links. Therefore, they shouldn't need access to any properties of those objects after they have been created.

[-] [email protected] 6 points 1 week ago

You can use user styles for that

[-] [email protected] 5 points 1 week ago

TIL, thanks

[-] [email protected] 49 points 1 week ago

For those who are curious about its history, this is where it all began for the visited links to be that color by default.

Date: Mon, 12 Apr 93 02:38:29 -0500

Subject: NCSA Mosaic 0.13 released.

  • Changed default anchor representations: blue and single solid underline for unvisited, dark purple and single dashed underline for visited.
[-] [email protected] 21 points 1 week ago

A dashed underline would make it a lot better and accessible. Don't think I've seen a browser do that by default

[-] [email protected] 21 points 1 week ago

I like to style visited links blue and unvisited links purple, just to mess with people.

[-] [email protected] 13 points 1 week ago

great example of a code smell, too! JS needs to know about styles?

shouldn't be styling in JS! make it asd/remove a class instead

need to know whether to load content or not? save it to local/session storage! don't make a server call if it already exists!

need to enhance your tracking? include it with your payloads as it happens, you're asking for race conditions

client side disabled local caching? great! working as intended. make a graceful fall-back

everything here is a short term problem that belies long term tech debt. tight coupling sounds sexy, but SOLID principals and The Law of Demeter exist to stop our codebases from rotting if we can't change it, then it's not software it's hardware

[-] [email protected] 8 points 1 week ago

JS needs to know about styles?

It's about JS trying to detect if the link was visited, not about style. People used to do that to evade cross-site tracking protection, and this is why JS isn't allowed to know that anymore.

[-] [email protected] 4 points 1 week ago

This. Did a seminar on these techniques during my it security degree. Porn sites invented that to detect people that use competing sites.

[-] [email protected] 1 points 1 week ago

hence the comment about tracking ;) anything more than recording your events as they happen are a security and privacy risk

[-] [email protected] 3 points 1 week ago

great example of a code smell, too! JS needs to know about styles?

shouldn't be styling in JS!

But what if I want to use JSSS?

[-] [email protected] 2 points 1 week ago

Sheesh, because of their colors at the bottom my mind interpreted purple and blue as purple and yellow and it got me hella confused

this post was submitted on 19 May 2025
258 points (97.1% liked)

Programmer Humor

23545 readers
2687 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS