5 ms·

I thought WebKit's WebCore would be to blame for this and not Chrome. Is it because Chrome (v3) is using outdated versions of WebKit or I am I misunderstanding

by walkon 17y ago

I thought WebKit's WebCore would be to blame for this and not Chrome. Is it because Chrome (v3) is using outdated versions of WebKit or I am I misunderstanding what WebCore does (very possible)?