Apple's documentation suggests using WkWebView for new development, although it does seem to have a typo where it recommends WkWebView through UIWebView on Mac.
For new development, use this class instead of the old UIWebView class.
The typo is probably due to the fact that they are trying to combine the OSX and iOS interface with the web view using the same header for both.
However, WkWebView does not have all the features that WebView has in OSX. For example, you can access DOM nodes in a native interface in WebView , but I see no way to do this from Swift / Objective-C to WkWebView .
For my purposes, it seems to me that WebView is what I need, but I'm tired of starting a project that relies on an API that will be removed. However, I see no mention of the intention to abandon WebView anywhere in the headers or documentation.
What is even more confusing, this WebKit Framework Link refers to both the WK and the older web interface APIs without specifying anything.
Wkwebview
The WKWebView object displays interactive web content, such as for a browser in an application.
Webview
WebView is the main view class in the WebKit structure that controls the interaction between the WebFrame and WebFrameView classes.
Does WebView to OSX?
source share