Linked by Thom Holwerda on Thu 2nd Jul 2009 12:19 UTC
KDE Whenever I use KDE, the part I dislike the most is the rendering engine used by Konqueror, called KHTML. KHTML just doesn't render pages as smooth and as well as Gecko and the KHTML fork WebKit, up to a point where I find Konqueror unusable as a web browser. However, work is underway to replace KHTML in Konqueror with WebKit, but according to KDE developer Adam Treat, this is a futile effort: Konqueror is too KHTML API specific.
Thread beginning with comment 371348
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: KHTML
by DaveDavtropen on Thu 2nd Jul 2009 17:08 UTC in reply to "RE: KHTML"
DaveDavtropen
Member since:
2009-03-20

They had two vulnerabilities in WebKit that allowed that one guy to win the Pwn2Own contest two years in a row. That's a HUGE number of vulnerabilities, especially compared to historically secure platforms like Internet Explorer.

In all seriousness, the WebKit team is pretty good at applying patches that people send in, but they have very little control over Safari's release schedule, since that depends more on Safari's proprietary interface and Apple's marketing schemes.

Any open source browser effort that uses WebKit is free to perform its own security vetting.

Reply Parent Score: 1

RE[3]: KHTML
by tyrione on Thu 2nd Jul 2009 20:02 in reply to "RE[2]: KHTML"
tyrione Member since:
2005-11-21

They had two vulnerabilities in WebKit that allowed that one guy to win the Pwn2Own contest two years in a row. That's a HUGE number of vulnerabilities, especially compared to historically secure platforms like Internet Explorer.

In all seriousness, the WebKit team is pretty good at applying patches that people send in, but they have very little control over Safari's release schedule, since that depends more on Safari's proprietary interface and Apple's marketing schemes.

Any open source browser effort that uses WebKit is free to perform its own security vetting.


You better include Opera, Firefox, IE7/8 and everyone else in those exploits.

Reply Parent Score: 3

RE[4]: KHTML
by modmans2ndcoming on Thu 2nd Jul 2009 21:18 in reply to "RE[3]: KHTML"
modmans2ndcoming Member since:
2005-11-09

since it was a Flash vulnerability.

Reply Parent Score: 2

RE[4]: KHTML
by segedunum on Sat 4th Jul 2009 10:58 in reply to "RE[3]: KHTML"
segedunum Member since:
2005-07-06

You better include Opera, Firefox, IE7/8 and everyone else in those exploits.

Why? It was made perfectly clear that those came about because of the ease with which Safari and the Mac allows you to assume certain things.

Reply Parent Score: 2

RE[3]: KHTML
by segedunum on Fri 3rd Jul 2009 19:41 in reply to "RE[2]: KHTML"
segedunum Member since:
2005-07-06

They had two vulnerabilities in WebKit that allowed that one guy to win the Pwn2Own contest two years in a row.

Correction. It was a vulnerability in Safari on a Mac, with the Mac being as helpful as possible in the process.

Reply Parent Score: 3