If an app needs a webview, it should always strive to open that view in an embedded Safari webview (called an SFSafariViewController) or link to the view in the

If an app needs a webview, it should always strive to open that view in an embedded Safari webview (called an SFSafariViewController) or link to the view in the user's own choice of browser. The app is prevented from seeing ‘inside’ this view. Sometimes an app needs to control some aspect of the external view - for instance listen to some Js event, or inject authorization - and this can be for totally legitimate reasons in the flow of the app. Then the application needs to use another type of embedded webview called a WKWebView, which by definition allows the app to see into the user's interactions in the embedded browser. Most developers and apps use these for totally necessary reasons - but Facebook is deviously abusing this functionality. Some of the posters in this thread are blaming Apple for Facebook's evil behavior, but a lot of totally legitimate functionality that needs this type of app/browser communication would be impossible without the ability to enable it for genuine and well-founded reasons.