• jol@discuss.tchncs.de
      link
      fedilink
      arrow-up
      30
      ·
      2 months 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.

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        16
        arrow-down
        1
        ·
        edit-2
        2 months 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.

          • Lucy :3@feddit.org
            link
            fedilink
            arrow-up
            9
            arrow-down
            4
            ·
            2 months 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.

  • said@lemmy.sdf.org
    link
    fedilink
    arrow-up
    49
    ·
    2 months 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.
    • MagicChicken@lemmy.world
      link
      fedilink
      arrow-up
      21
      ·
      2 months ago

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

  • orockwell@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    2 months 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

    • mmddmm@lemm.ee
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      2 months 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.

      • nomad@infosec.pub
        link
        fedilink
        arrow-up
        4
        ·
        2 months ago

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

      • orockwell@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

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

    • sik0fewl@lemmy.ca
      link
      fedilink
      arrow-up
      3
      ·
      2 months 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?

  • tuxiqae@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month 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