• troybot [he/him]@midwest.social
      link
      fedilink
      English
      arrow-up
      28
      ·
      5 months ago

      Looks like the article was updated today. I’m guessing this was originally covering an announcement for a future rollout and now it’s finally happening?

      • TrickDacy@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        2
        ·
        5 months ago

        Maybe. Confusing decision on the part of Mozilla though, if so. I was checking to see if they mentioned which version this update happened in, but couldn’t find it. Then I noticed the original post date. Weird.

        • EngineerGaming@feddit.nl
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 months ago

          Depends on how it “goes too far”. What I am, for example, afraid of is the possibility of removing Manifest V2 support. Maintaining the browser with such a significant change would get more and more difficult as time goes on.

          • verdigris@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 months ago

            This is currently one of the biggest selling points for the browser, since Chrom(ium) is dropping support for v2… So I don’t see that happening.

            • EngineerGaming@feddit.nl
              link
              fedilink
              English
              arrow-up
              1
              ·
              5 months ago

              Sure hope so! But sadly, I think this is a possibility - iirc they were working on a different implementation of Manifest V3, so I fear that it might still happen eventually, “for the sake of security”.

        • morriscox@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          5 months ago

          Firefox did an add-on genocide years ago and it obviously didn’t hurt them in the long run.

        • unemployedclaquer@sopuli.xyz
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          7
          ·
          5 months ago

          I agree, but something will have to change because chrome will swallow ALL that. Just today some back-end problem was messing up all my stuff, and co-workers were asking, " did you try a different browser? " botch no I did not try Netscape

          • TrickDacy@lemmy.world
            link
            fedilink
            English
            arrow-up
            6
            ·
            5 months ago

            “I agree [with the opposite of what you said]. Also, here, have an irrelevant anecdote that includes a funny misspelling and a supposed diss of FF from 1999”

            • Esp@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              3
              ·
              5 months ago

              Personally, I remember chrome always flash banging me when on a website with a dark background and I clicked to the next page because apparently clearing the page to the same RGB value as what is set as the HTML background is too hard so they just always clear with pure white. But they did have a faster JS engine. Not sure anymore, haven’t given enough of a shit to try anything but firefox in years now.

            • unemployedclaquer@sopuli.xyz
              link
              fedilink
              English
              arrow-up
              1
              ·
              5 months ago

              I meant, talking to coworkers, – yes, I already tried Chrome, Edge, etc, not sure what etc would include - not worth it to explain what little I know of Chromium, and it doesn’t matter. I’m aware it’s Chromium or Firefox in getting a page to work. Random coworkers, they don’t know or care.