Sorry if this was a joke and I didn't spot it. Chrome was based on WebKit which was itself based on KHTML if memory serves. Chromebooks are based on a version of that outside engine running on top of Linux which they also didn't create.
The process model was the novel selling point at the time from my memory [1].
Which uses the WebKit engine and is kindof a showcase for Safari, granted, but it still exists as distinct browser under that name.