Chrome's Manifest V3 transition is here. First up are warnings for any V2 extensions.

Reminder to switch browsers if you haven’t already!

  • Google Chrome is starting to phase out older, more capable ad blocking extensions in favor of the more limited Manifest V3 system.
  • The Manifest V3 system has been criticized by groups like the Electronic Frontier Foundation for restricting the capabilities of web extensions.
  • Google has made concessions to Manifest V3, but limitations on content filtering remain a source of skepticism and concern.
  • @[email protected]English
    5•6 months ago

    I deleted my original comment before you replied because I am not really in the mood to defend this but the OP was talking about the pain of developing for different browsers and I don’t care what is a fork of what, this is a fact: Chrome, Firefox and Safari all render differently and have to be catered to individually.

    Also, Safari, between desktop and mobile, has 30% of the market to Firefox’s 8%.

    I don’t LIKE it, but there are “effectively” three, not two, rendering engines.

    • @ricdehEnglish
      1•6 months ago

      It’s about browser architecture and not silly names (“Safari”, “Firefox”, “Chrome”). The point is that there are only two actual variants.

      • @[email protected]English
        4•6 months ago

        Not when you have to make a web app render identically in them, which is what the OP was about.

      • @DewayEnglish
        2•6 months ago

        No, you still have three rendering engines. WebKit and Blink are different. Since the second is an (old) fork of the other one, they are similar but far from being the same. They are pages that work in one but not the other, even if you change the user agent.

      • @ripcordEnglish
        1•6 months ago

        That’s…not true at all.