Bug 190961
| Summary: | Feature Request: Expose Content Blockers in WKWebView | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Thomas Steiner <tomac> |
| Component: | WebKit API | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Enhancement | CC: | achristensen, bfulgham, ggaren |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 12 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 12 | ||
Thomas Steiner
Content Blockers (https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/ContentBlocker.html) allow users to block unwanted content like social widgets, trackers, etc. Currently, this functionality is exposed to SFSafariViewController as well as Safari itself, however not to WKWebView. While developers can in theory reimplement their own content blocking rules (like, for example, in the Brave browser: https://brave.com/features/), the user through their system-level Content Blockers has already expressed their blocking choices, so it would be desirable if they were respected universally.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brent Fulgham
This request was also logged as the following radar:
<rdar://30559074>
There are currently no plans to expose system provided Content Blockers outside of Safari/SFSafariViewController.