> apps with in-app webviews can roll out a custom engine, but otherwise it uses WebKit regardless of default browser. It should obviously use the webview facili

> apps with in-app webviews can roll out a custom engine, but otherwise it uses WebKit regardless of default browser. It should obviously use the webview facility provided by the default browser, if it offers one. This has massive potential to break an unbelievable number of things, first-party and third-party alike. WebKit is used in all sorts of places people wouldn’t expect, for example at one point UILabel (the native control responsible for displaying non-scrolling text and labels) used WebKit under the hood for rendering attributed strings.