• sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    3 days ago

    I feel you. I use Firefox on Android (technically Mull), and it’s generally pretty good. It does seem like some sites don’t work properly on mobile Firefox that work fine on desktop, but I haven’t looked into why (and I’m guessing it’s those missing features you’re talking about).

    • TachyonTele@lemm.ee
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      3 days ago

      Im guessing the website hasn’t been optimized for mobile.

      You’re blaming your car for the roadwork.

      • redfellow@sopuli.xyz
        link
        fedilink
        arrow-up
        3
        arrow-down
        10
        ·
        3 days ago

        I’m blaming a browser that hasn’t implemented as many standards as it’s competitors, and choosing therefore to use a free car that runs well on said roads.

            • kattfisk@lemmy.dbzer0.com
              link
              fedilink
              arrow-up
              2
              ·
              edit-2
              2 days ago

              How many of these “lacking features” are actually standardized? Of course some draft under development by Google will only work in the latest version of Chrome. It might not even work in future versions of Chrome, since it’s not standardized.

              If you built something that requires such a feature, it’s you who is choosing to write code that is incompatible with the standards and only works on a particular browser version. You can’t blame others for that.

            • TachyonTele@lemm.ee
              link
              fedilink
              arrow-up
              4
              arrow-down
              3
              ·
              edit-2
              3 days ago

              I’m sorry. I don’t think you understand the relationship between a browser and a websites settings.

              If a website is not made to be compatible with a certain browser, that is the websites fault. Not the browser.

              That link is a wall of checkboxes with no explanation, btw.

              (Also, not touching Chrome. Pretty sorry for you that you’re defending it so much.)

              • redfellow@sopuli.xyz
                link
                fedilink
                arrow-up
                3
                arrow-down
                3
                ·
                3 days ago

                Like i said earliier, im a web dev, and that’s a list of web standards, and a comparison which browser has implemented which spec.

                You literally said you don’t understand them, so maybe brush up on the subject you are discussing instead of telling others how things are?

                I’m not defending anything, just providing info and saying why I use what I use.

                If a browser is missing official standards features, then the browser is objectively lagging behind. Yes, the web devs are at fault for using things that lack wider support, but that comes down to many factors such as having the time and money to implement things in a more complex manner to support more browsers. That’s not always feasible or possible if a certain core feature lets us save hours or days.

                  • VeryVito@lemmy.ml
                    link
                    fedilink
                    arrow-up
                    2
                    arrow-down
                    2
                    ·
                    2 days ago

                    When the browser can’t perform its end of the deal? Certainly. I don’t blame Netflix for no longer supporting IE5, either.