• SatyrSack@quokk.au
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      What is the implication there? That your browser is out of date? Or is that a greater problem with your OS itself?

      • TootSweet@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        10 hours ago

        You know, I don’t know.

        But I think “problem” is probably a strong word. I probably just need to install something or upgrade my browser if I want that emoji to render nicely.

        I’m guessing calling this a “problem” would be like calling it a “problem” that you can’t open .blend files because you haven’t installed Blender.

        But also, I wouldn’t be surprised if most browsers can’t necessarily render absolutely all emojis. Surely there’s a bit of lag between the formalization of new emojis and wide support. For instance, does your browser render these?

        I picked these in particular because they’re all part of “Unicode 17” which is the “latest batch” of Emojis to be made part of the unicode standard by the Unicode Consortium in September 2025. If any browser aren’t yet universally supported, it’s probably some from that set.

        Of course, September 2025 is a while ago. It may well be that these are already widely supported.

        But then again, the Jellyfish is from Unicode 15 back in September of 2022, so maybe a bit old. I am currently using Raspian, and I doubt it’s terribly bleeding edge, so maybe that’s it. I’ll update my browser to the latest offered by Raspian and see what that does.

        Edit: Nope, updating my whole Raspian system (including updating Firefox to 153.0) didn’t change anything. Then again, I’m not sure what determines what emojis render and what emojis don’t. 🤷 Maybe there are “emoji fonts” or something.