Khtml loveletter

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Khtml loveletter
by micha on Monday 17/Jul/2006, @01:15

Konqueror is "my" browser for ages now, using it every day. I am developing web apps using konqueror first, checking other browsers later. I am convinced by its good-naturedness. I have seen other browsers fail in obscure ways, even firefox, even safari, where khtml just works fine. Note, this is addressed to khtml, not kjs.

Devs out there, keep up the good work, but don't mess things up, please. From a user's perspective, I have the impression that khtml is just fine as it is, but javascript and dom needs to catch up. So it seems as though merging with webkit is too radical as a cure. Issues can be pin-pointed quite precisely and they are already in the bugs database, I think. Don't pull out the merge sledgehammer as "the next logical step".

Related Links

·   Articles on Konqueror
·   Also by micha
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Khtml loveletter
by Carewolf on Tuesday 18/Jul/2006, @13:07

The few big things that make it hard is:
Rich text editing, which is very hard and something WebCore has
and:
The same bugs as WebCore, we are assumed by websites to act the same or not detected at all. We need to be detected and support the same bugs as what we are detected as.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"If you have an itch not being scratched, you can scratch it, or pay someone to scratch it for you." -- Eric Laffoon
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.