1065
Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com)
submitted 2 years ago by to c/technology@lemmy.world
357 comments fedilink hide all child comments
 

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.
you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 2 years ago* (last edited 2 years ago) (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (3 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent