If Apple did not want this, they could have just not put in the effort on two platforms. Apple even added Content Blocking to iOS, which I have been very thankful for. If Apple did not want ad blockers, they would not have gone so far as to create the Content Blocker API which is relatively new. However, AdBlock is just as fast in Safari 12 as it was in Safari 11. That's one of the reasons Apple wants developers to use the Content Blocking API exclusively. It is true that the newer Content Blocking API is faster than the old canLoad API, which has been deprecated in Safari 12. Apple wasn't able to approve the release in time to avoid the rude awakening that happened when Safari 12 started rolling out.įact check: Does AdBlock slow down web browsing in Safari 12? No.
SAFARI ADBLOCK REDDIT UPDATE
Nearly two weeks ago, we submitted an update that removed that API specifically so our users would not be adversely affected. We and other developers have been preparing for this for months. Any ad blockers that still include the deprecated API are automatically disabled. Safari now supports only the Content Blocking API introduced in Safari 9. Starting with Safari 12, Apple is deprecating the canLoad API that ad blockers like AdBlock, Adblock Plus, and uBlock Origin have traditionally used. There is a help document on the AdBlock (different extension) site that says (bold emphasis is mine): Apple is not preventing uBlock from existing, just from using that API. I said that Apple will remove support for the specific "canload" API that uBlock has been using. But I agree that Safari will eventually stop uBlock Origin and all other ad blockers, but their own.so much for freedom
0 kommentar(er)
