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.
  • rottingleaf@lemmy.zipEnglish
    2·
    6 months ago

    Better for MS non-standard things? Or better how? Performance-wise - yes.

    IMHO a web browser has to support HTML 4.* , JS, Netscape plugins (Java, Flash, whatever else) and that’s it.

    That’s what I came to when I started using the Web, but I’m confident it’s not just bias - that was the best combination. I’m not sure on CSS - I hated it, but people have good arguments in favor of it. But hypertext with limited appearance tuning and scripts for the web itself, plus plugins for various content, including applications, - that’s definitely a better idea than the modern approach.

    • dan@upvote.auEnglish
      1·
      6 months ago

      Better for MS non-standard things? Or better how?

      All browsers had non-standard things back then, to the point where many sites had two versions: An IE version and a Netscape version.

      Believe it or not, back then Internet Explorer was the most standards-compliant browser. It was the first browser to implement the DOM and CSS based on relevant W3C specs (Netscape was backing JSSS instead).

      Many features we take for granted these days came from IE. Drag and drop, the JS events system, iframes, rich text editing, clipboard access, AJAX (dynamically loading content on the page without a full page reload), visual effects like transparency and gradients, all originally came from Internet Explorer.

      The CSS box-model in IE6 (including margin, padding and border in the width of elements) was wrong because the CSS spec hadn’t been finalized by the time of its release so Microsoft used a draft, and it changed from publication of the draft to publication of the final version. Many years later, people realised that IE6’s model was actually the better model, which is why every browser supports it now via box-sizing: border-box.

      • rottingleaf@lemmy.zipEnglish
        1·
        6 months ago

        Sigh. OK, since I didn’t use Netscape (started around 2002), didn’t know about some of these.