Earlier quoted context omitted.
Is a rendering engine still a web browser if you remove all the chrome and extra features built around the rendering engine? I would say not. And it has a rendering engine: the iOS WebKit engine. It’s not Google’s preferred rendering engine and Chrome isn’t my choice of browser well, anywhere at all actually, but it’s still a functional web browser.
> Is a rendering engine still a web browser if you remove all the chrome and extra features built around the rendering engine? > I would say not. No, obviously not. If Apple were to allow third-party web rendering engines but disallow third-party web chrome that would be equally ridiculous. But just because one part of a browser is important doesn't mean that other parts of a browser aren't also important. > And it h…
Sure, but both halves are still there. WebKit is just filling in for Blink.
> but it's not "Google's wildly popular web browser".
You want to know the screwed up part? It actually is. There’s no gun to Google’s head to list any web browser at all for iPhones in the App Store, but they do, and they themselves chose to brand it exactly the same as their desktop and Android browser; and that’s exactly how people perceive it: Google Chrome. It’s also wildly popular. I ask people about it sometimes when I see them using it and all that geeky crap that you and I know about how it’s not the same as Google’s “real” browser is beyond them. They don’t care and it’s just Google Chrome to them.
> It may be a functional web browser (honestly arguable given how old and buggy the iOS rendering engine is)
WebKit is still a top class rendering engine and only about as buggy as any other rendering engine. Blink is of the same lineage given it is a fork of WebKit and Gecko is even older.