APIs for content filters

Originator:bnicholson
Number:rdar://23284825 Date Originated:10/27/15
Status:Open Resolved:
Product:iOS Product Version:
Classification: Reproducible:
 
Safari (and SFSafariViewController) support compiled content blocking lists for filtering pages, and it would be very useful for WKWebView to support these blocking lists for the same reasons. 

Our particular use case for Firefox for iOS is to support tracking protection lists, and there's currently no way to intercept requests made via WKWebView. An API like NSURLCache may also be useful if it worked with WKWebView, though the existing private content blocking API has a number of advantages, as it can:

1) determine the origin of the request (for blocking third-party content),
2) determine the types of resources being requested (presumably based on the DOM element requesting the resource), and
3) work with existing iOS content blocking extensions.

Privacy is, of course, extremely valuable to Mozilla and our users, so having some degree of control over requests that websites are making will be important for us moving forward.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!