No, I was asking about "just a fork of khtml". That implies that there wasn't meaningful work. WebKit is at this point (and probably a decade ago) a functionally complete rewrite.

When webkit forked KHTML, KHTML couldn't render the vast majority of the top 100 websites properly, just by the time the first safari was released webkit was already able to render those correctly, or in many cases even usably.

When I say WK rendered correctly, I mean matching Firefox/Explorer, not just a bare "is useable".

Not saying you are wrong, but I remember that KHTML was the first renderer that was able to pass the ACID2 test. So this doesn't sound right to me