Google ramps up its campaign against ad blockers on Chrome.
  • Google is transitioning Chrome’s extension support from the Manifest V2 framework to the V3.
  • This means users won’t be able to use uBlock Origin to block ads on Google Chrome.
  • However, there’s a new iteration of the app — uBlock Origin Lite, which is Manifest V3 compliant but doesn’t boast the original version’s comprehensive ad-blocking features.
  • Chozo
    21•4 months ago

    Nearly 3.5 billion people do.

    “Does anybody still use [literally the most popular product in its industry]?”

        • @[email protected]
          -9•4 months ago

          I’m so elite because I choose to use a browser that respects my privacy lol.

          Thank you, I guess?

      • Chozo
        2•4 months ago

        I deserve ads because Firefox won’t render any of the web apps I use for work? Damn.

          • Chozo
            3•4 months ago

            Firefox breaks Slack, Zoom, Salesforce, Jira, and several other internal/proprietary platforms I use. Many of our tools are integrated into each other (sometimes on the backend through the API, sometimes on the frontend through an iFrame), and Firefox really doesn’t play nicely with these interactions. Either it doesn’t like the fact that our apps are accessing multiple sites at a time and throws security errors, or it just doesn’t render some parts of the page properly, making them unusable.

            For instance, one ticketing tool we use is completely inaccessible in Firefox, because the page breaks after the header and loads the rest into a 10px-wide column that stretches for miles. Works fine in Chrome, Edge, and even Safari somehow.

            Some of this could be fixed by using these platforms with their out-of-the-box software which may be more compatible with Firefox, without our modifications. But our mods are there because these integrations drastically improve our workflows, so that’s unfortunately not a feasible option for our business.

            A lot of this is due to Firefox having stricter standards, which isn’t necessarily a bad thing. Maybe our developers should make our tools more standard-compliant and that might be better in the long run. But until then, I gotta use what works.

            • The Octonaut
              -4•4 months ago

              Firefox breaks…

              (Long unnecessary nonsense that isn’t applicable to anyone else)

              Maybe our developers should make our tools more standard-compliant

              lol. So who broke it?

              • Chozo
                3•4 months ago

                (Long unnecessary nonsense that isn’t applicable to anyone else)

                I was answering a question that was asked directly to me, genius.

          • @ShortFuse
            3•4 months ago

            Firefox, unfortunately, has been lagging behind. Safari is close to surpassing Firefox if they haven’t already. Safari really made a big shift for actually implementing web standards around 16.4.

            • No HDR - relevant for me because I mod PC games for HDR
            • Dropped PWA on desktop - even Apple went full 180° and embraced it now on Mac OS X. Chrome really gets a good push from this from Microsoft constantly helping push more app manifest stuff since it appears one of their goals is to render more things over Edge PWAs (eg: like the title bar), and resort less to having to use electron.
            • No masked borders - can’t do custom element borders like corner cutting or perfect squircles. Rounded edges only

            Chrome is still the absolute best for accessibility. Neither Firefox nor Safari properly parse the aria labels when it comes to how things are rendered. Chrome will actually render text in accessibility nodes as presented on screen (ie: with spacing). Safari and Firefox only use .textContent which can have words beingmergedwhentheyshouldn’t.

            Chrome also has Barcode and NFC scanning built right in. I’ve had to use fake keyboard emulators for iOS. Though, Chrome on Mac OS X also supports it. Safari has native support for Barcode behind a flag, so it’ll likely come in the future. Barcode scanning is still possible with Firefox through direct reading of the camera bitmap, which is slower but still good. There’s no solution for NFC for Safari, but if Chrome ever comes iOS, that would possibly be solved. I believe Face Detection is similar, but I’ve never used it.