3 ms·

>I have yet to see where Chrome is explicitly telling anyone they plan to phase out support for adblockers, nor where they are making it clear that is their int

>I have yet to see where Chrome is explicitly telling anyone they plan to phase out support for adblockers, nor where they are making it clear that is their intention. That was never their intention, not what the uproar was about, so it's to be expected that you're not seeing any evidence of it. The problem with Manifest V3 is not that it disables adblockers; not sure where you got that idea from. The problem is that it severely restricts how effective they can be. Many of the things uBO does cannot be done in v3. That's what the uproar is about. https://github.com/uBlockOrigin/uBlock-issues/issues/338#issuecomment-456171375 https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss... https://github.com/uBlockOrigin/uBlock-issues/issues/338#issuecomment-873602429 https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...

encryptluks2 5y ago
Again, these changes aren't taking place until 2023. They are still accepting new features. Yes, everyone is aware that the developer of uBlock threw a fit. It was all over the news, and it was portrayed by the media as Chrome is disabling adblock, because that is essentially the message from Raymond Hill at the time. I think it is good to be aware of these changes, and contribute feedback and try to get compatible or comparable APIs implemented. At no point has Google or Chromium said they are unwilling. If anything, it looked like a prime opportunity for them to scream fire when there was no fire.