• the_doktor
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    So copy and paste it into something else on your computer if you’re too blind to see the difference in letters in that font (I can tell, easily) and tell it to use another font. PEBCAK issue, not a real one.

    • solrize@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      This is on my phone (Android Firefox), not the computer (desktop Firefox). Yes some of the characters in the font are indistinguishable. That’s why there’s a ticket open after all. And even if crappy workarounds exist, it can and does still suck. Thus, JMINS.

      Why do you defend this crap? I never understand what makes people do that.

      • the_doktor
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        “FIREFOX SUX BECAUSE MY OUTSIDER 0.00000001% USE CASE AND I OPENED A TICKET BOOHOO!”

        This is how you sound. Just because there’s a ticket open for outlier bullshit doesn’t make it valid to gripe about endlessly, especially when there are so many possible, simple ways around it. Slightly annoying does not mean broken.

        Phones have copy/paste, by the way.

        • solrize@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago
          1. I didn’t open that ticket. I encountered the issue, went to the tracker, and found there was already a ticket open.

          2. Tickets have priority labels. The existence of a workaround like pasting the password to a program with a different display font means this bug is not a showstopper. That doesn’t mean it is not a bug.

          3. No it’s not just this one bug. There are plenty more. I can link more tickets if you want. I was going to do that but the discussion about the password font bug spiralled.

          4. What is happening is mostly an attitude problem, it seems. People like you, seeing a code bug, instead of fixing it (or in this case at least recognizing that it should be fixed), go around searching for rationalizations for leaving it unfixed. It being unfixed while Mozilla continues to bloat up the browser with more new crap is instead evidence of Mozilla’s priorities being screwed up.