>> Is a rendering engine still a web browser if you remove all the chrome and extra features built around the rendering engine?

> Is that supposed to be a counterargument?

Only as much as what I was responding to was an argument.

> If you can't replace the rendering engine, then you're not able to install your own web browser.

Except that is literally not true if a rendering engine is available to you to use.

> Which is replacing the one that was removed.

“Removed” would imply there was ever another rendering engine in use on Chrome for iPhones. The Chrome that is in the App Store now is one that Google chose to ship and call Chrome. People like and use it too.

I think we can agree that WebKit is being subbed in over Google’s preferred choice of rendering engines though.

What you said could be the start of a counterargument to someone that says renderer==browser.

But they never said that. Their argument only depends on replacing the renderer being a sometimes-necessary component of installing your own browser. Talking about replacing the renderer but not the UI is a thought experiment that doesn't counter that.

> Except that is literally not true if a rendering engine is available to you to use.

Only if everyone agrees with your personal definition of browser. Many people don't.

> “Removed” would imply there was ever another rendering engine in use on Chrome for iPhones.

No, it just implies their starting point for making their iOS browser included the chrome codebase.