I can give a short summary about the current status of khtml.
Html4: about 95% implemented.
CSS1: about 80%-90% implemented. Only very few properties are still missing.
CSS2: about 40%. Together khtml's CSS support is not far away from what IE5 on windows offers.
DOM Level 1: Almost complete. The HTML part is completely implemented, a few thigs specific to XML are still missing.
DOM Level2: The CSS part, traversal and ranges are implemented. Still missing are the events. This means about 70% is implemented.
Support for java applets is mostly complete.
Netscape plugins (flash, real player, etc) work.
Javascript: The core (ecma-262 version3) ist almost complete, but the DOM bindings still need some work.
khtml has support for bidirectional scripts (hebrew and arabic).
it is pretty fast:-)
khtml is still a bit buggy on some pages, but we expect to get that fixed until the release of KDE2. As long as you don't need too much javascript it is already very useable and many people are using konqueror as their main browser.
You might be interested in this page: http://www.people.fas.harvard.edu/~dbaron/css/test /results It shows a comparison between several browsers, including Konqueror, regarding CSS, CSS2, etc...
Unfortunately it still shows the results for an old version of khtml. I once checked the version now released as beta2, and it scores somewhere between -7 and -15 points (which is where IE5 for windows is located:-) Especially all the crashes reported there have now been fixed.
Let me try to answer your questions about the current status of khtml (the html rendering engine of konqueror):
You can use aswell as to include html subpages. Or do you mean including the html directly? This is nowhere defined in the HTML standards AFAIK.
CSS positioning is supported except for fixed, but I'm confident we'll have that working by the time we release KDE2.
CSS2 support is however far from being complete.:before and:after pseudoclasses are still not supported, neither is the text-shadow property. But to be honest, there isn't a single browser out having support for text-shadow, the same is true for a lot of other CSS2 properties.
PNG alpha channels are not supported, but that is a limitation of X11 rather than konqueror. One could in principle work around that, but the price to pay for it is quite heavy, since one has to get the pixmap below the image from the server, blend the image on top and send the result back to the server. This would slow down rendering more than I am willing to compromise on for such a feature.
I'm not quite sure what you mean by XML namespace selection in CSS2 sheets. Anyway, khtml unfortunately still doesn't have support for XML (xhtml is supported however), just because the developers we have are booked out with other things.
Slashdot Mirror
khtml is still a bit buggy on some pages, but we expect to get that fixed until the release of KDE2. As long as you don't need too much javascript it is already very useable and many people are using konqueror as their main browser.
Lars
Unfortunately it still shows the results for an old version of khtml. I once checked the version now released as beta2, and it scores somewhere between -7 and -15 points (which is where IE5 for windows is located :-) Especially all the crashes reported there have now been fixed.
LarsLet me try to answer your questions about the current status of khtml (the html rendering engine of konqueror):
:before and :after pseudoclasses are still not supported, neither is the text-shadow property. But to be honest, there isn't a single browser out having support for text-shadow, the same is true for a lot of other CSS2 properties.
You can use aswell as to include html subpages. Or do you mean including the html directly? This is nowhere defined in the HTML standards AFAIK.
CSS positioning is supported except for fixed, but I'm confident we'll have that working by the time we release KDE2.
CSS2 support is however far from being complete.
PNG alpha channels are not supported, but that is a limitation of X11 rather than konqueror. One could in principle work around that, but the price to pay for it is quite heavy, since one has to get the pixmap below the image from the server, blend the image on top and send the result back to the server. This would slow down rendering more than I am willing to compromise on for such a feature.
I'm not quite sure what you mean by XML namespace selection in CSS2 sheets. Anyway, khtml unfortunately still doesn't have support for XML (xhtml is supported however), just because the developers we have are booked out with other things.
Cheers,
Lars