• SnowdenHeroOfOurTime@unilem.org
        link
        fedilink
        arrow-up
        9
        arrow-down
        1
        ·
        1 year ago

        Yeah. They selectively adopt web standards years later than the others and the mobile and iPad versions in some ways behave completely differently from desktop (and each other). If safari just acted like the other browsers, frontend web dev would be MUCH easier.

        • SpeziSuchtel@feddit.de
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          edit-2
          1 year ago

          Depends on which standards, for some css functions like backdrop-filters and mix-blend-modes it was years ahead of Firefox, where some of those had to be activated through about:config. I‘m glad Firefox catchend up in the past few years though. Also WebKit accelerated HTML5 adoption a lot.

          Never had any major issues developing for Firefox, safari and chrome in the past few years though. It was quite a different story 10 years ago but nowadays 99% of the time, it works flawlessly between all major browsers for me.

          • SnowdenHeroOfOurTime@unilem.org
            link
            fedilink
            arrow-up
            3
            arrow-down
            4
            ·
            1 year ago

            I feel like you’re referring to Firefox literally 12 years ago or more. I’m talking about today. Literally any brand new standard is not supported for 1-2 years minimum. I run into problems with safari on a near daily basis. I rarely have a weird issue in Firefox. 99% of the time chrome and Firefox behave the same. The vast majority of the time that one browser has an issue others don’t, it’s safari. It’s weird to me to get pushback on this …

            • SpeziSuchtel@feddit.de
              link
              fedilink
              arrow-up
              6
              arrow-down
              1
              ·
              edit-2
              1 year ago

              Backdrop filters were introduced with Firefox 103, which was released just 12 months ago. And it was a major pain for me that Firefox was the only browser I had to do workarounds for this function when Safari supported it since 2015 and chrome did since 2019.

              Every platform has some problems. But it’s fairly rare for me to run into these nowadays. I still love using Firefox. But just because your experience is different than mine doesn’t mean that mine is outdated. It’s not meant to be a pushback against your comment, just sharing that there had been issues with Firefox in the past as well.