|
|
|
|
|
|
by gcp
3421 days ago
|
|
|
Curious why you'd want safari's content blockers to run inside chrome or firefox though? That's not how browser plugins work anywhere else Because there's currently no way for those browsers to get any content blocking without switching to the slower WebView. I'm fairly confident that both the Google Chrome team and Mozilla's Firefox for iOS team are better informed here than you are. |
|
|
Apple has decided that Content Blocking is a Safari only feature. Apple has made the decision to not expose the private APIs in WKWebView that would allow browsers like Chrome and Firefox to use the same speedy content blocking.
The old WebView, UIWebView, also does not support content blocking. But since it runs completely in the same process as your app, you can replace the HTTP handling with your own and patch content blocking on top of that.
That is what Firefox Focus and Brave do for example. It works, but it is far from ideal. Also, it is likely an API on the way to be deprecated.