We'll have to wait and see whether the developers will modify their existing extensions to use the now built-in content blocking functionality, or continue with their existing code.
There wouldn't really be any benefit to developers of existing blockers, IMO.What would be the benefit if any if developers modified their existing Extensions to use the now built in content blocking functionality in El Capitan? Would it really make any difference?
There wouldn't really be any benefit to developers of existing blockers, IMO.
As far as I know, extensions specifically for the content blocking functionality, may simply be nothing more than a set of instructions on what to block.
I was under the impression that content blockers allow better control of "content" not exclusively ads. Like that post in the Macbook Pro forum section about a pop up disabling Safari, wouldn't content blockers (as implemented in El Capitan) block those elements as well? iOS 9 content blocking is more than just a set of instructions as it seems each content blocker apps block content different (a mouthful of content sorry). Rather than leave white space, it seem content blocker removes elements which is IMO a better implementation.There wouldn't really be any benefit to developers of existing blockers, IMO.
As far as I know, extensions specifically for the content blocking functionality, may simply be nothing more than a set of instructions on what to block.
Extensions specifically made for the new content blocking functionality may still be a set of instructions, because an instruction set can be more than just a list of what to block. It can include instructions on how to block the content.I was under the impression that content blockers allow better control of "content" not exclusively ads. Like that post in the Macbook Pro forum section about a pop up disabling Safari, wouldn't content blockers (as implemented in El Capitan) block those elements as well? iOS 9 content blocking is more than just a set of instructions as it seems each content blocker apps block content different (a mouthful of content sorry). Rather than leave white space, it seem content blocker removes elements which is IMO a better implementation.
I have uBlock installed and pop up blockers on but this website still throws an annoying pop upExtensions specifically made for the new content blocking functionality may still be a set of instructions, because an instruction set can be more than just a list of what to block. It can include instructions on how to block the content.
Existing content blockers do allow for finer control, because one thing they realised is that their filters aren't perfect, so the option to manually add an element, ad or not to the filter is often present.
Each existing blocker works differently, and the one I use doesn't leave a whitespace when it blocks elements, and I don't know of one that does, because I was satisfied with the first one I tried.
Many modern browsers by default block unsolicited pop-ups without any extensions, so unless that person unchecked the box to do that, I'm not sure how that could have happened.
I'm kinda partial to GlimmerBlocker. El Capitan claims it's incompatible, but it runs just fine after you reinstall it.
Apple has a list of verified Safari Add-Ons. Go here: https://extensions.apple.comI understand how to get content blockers for iOS 9, but where do you download them for Safari in OS X El Capitan?
Thing is AdBlock is not using the new "content blocker" mechanism, it is using the old extension method and won't be as efficient and fast. There is a good article here explaining the benefits of the content blocker method.Apple has a list of verified Safari Add-Ons. Go here: https://extensions.apple.com
The very first one is ad block