Talk:KHTML
From Wikipedia, the free encyclopedia
I redirected WebCore to this article. I take it WebCore and KHTML are the same?
hoshie 15:48, 3 Sep 2003 (UTC)
- No. In fact, there is WebCore, WebKit and KHTML. So the current redirect is wrong. I'm not sure of the details, since I'm no expert. There is something of an explanation in Safari (web browser).--Chan-Ho Suh 11:50, Sep 13, 2004 (UTC)
Contents |
[edit] SecurityFocus cite
On 01 Nov 2004, this article was cited in a SecurityFocus article on phishing. Securiger 06:50, 8 Nov 2004 (UTC)
[edit] Open-source divorce for Apple's Safari
Maybe worth mentioning in this article [1]. --minghong 18:34, 12 May 2005 (UTC)
- Maybe once this actually results in something. This all started with one of the KHTML devs complaining that other people were expecting WebCore changes to automagically pop-up in KHTML. [2] Since then it was mentioned in a few blogs and now it has been picked up by the tech media and somehow (chinese whispers) turned into a "divorce" between the KHTML and WebCore teams.
- We already cover the fact that the two trees are diverging. Nothing has changed. AlistairMcMillan 19:38, 12 May 2005 (UTC)
[edit] Apple
I made a seperate section about the relationship between apple and KHTML.
The presentation of the information as one big paragraph made it hard to read, so I split it into two. It still might be a bit hard to follow; rewording the section might be in order. --Starwed 21:52, 1 December 2005 (UTC)
[edit] not true
it is NOT true that the support for the acid2 test was based upon patches from apple, the khtml project created that themselves, as the stuff they got from apple was useless —The preceding unsigned comment was added by 80.196.156.209 (talk • contribs).
So fix the article, with a citation. -- Jon Dowland 08:46, 27 July 2006 (UTC)
[edit] Why KHTML
I wonder why KDE is spendding effort on KHTMl and does not use Gekko and joint the effort on Gekko for a faster improvement? 134.157.170.184 13:56, 22 March 2006 (UTC)
- I, on the other hand, wonder why Mozilla spends effort on Gecko instead of switching to KHTML and contributing to it. --Shutranm 00:32, 16 July 2006 (UTC)
- KHTML has a much better standards compilance level than Gecko. Besides, in open source world, "competition" (notice the quotes) between projects usually makes both of them stronger. See KDE and Gnome, cdrecord and cdrdao, mplayer and xine, emacs and vim... --Pmbarros 21:36, 28 July 2006 (UTC)