4 ms·
> embedded engine. I might be wrong but iOS decided from the early days to separate safari and webview. What would be interesting to know is if it is two diff
by oneweekwonder 9y ago
> embedded engine.
I might be wrong but iOS decided from the early days to separate safari and webview.
What would be interesting to know is if it is two different libs/renders/codebases or just degradation of features as op pointed out with webview, etc.
- Klathmon 9y agoFrom my research when I had this issue, (and i'm going from memory here, so forgive any inaccuracies) it looks like it's because Safari uses Safari's rendering engine, while WebView's use "WebKit" with a lot of modifications. As far as I heard from various sources, they are in many ways completely separate codebases, and the reasoning is that since WebKit is very tightly integrated with the OS, it takes them much more time to include new features into WebKit than it does in Safari.