I'm making this thread because I'm a bit confused about the differences between Konqueror and ReKonq, in light of the need for a good Firefox/Chrome alternative going forward (so not just a KDE question, but as a loyal KDE user I'd really like to use a Qt browser). I've been using Qupzilla as a browser for awhile now, but they recently announced that browser is switching to being Chromium/QTWebEngine based, something I'm not interested in. Anyway, I used Konqueror as my default browser for many years in the mid 2000's, but gradually less sites seemed to work with it, and I switched to Qupzilla.

Well, I gave Konqueror another shot with the WebKit engine, and am largely satisfied with it over ReKonq, but there are still some pages that don't display properly. I wouldn't be that worried about this, but the recent announcement of Mozilla implementing Adobe's HTML5 DRM sandbox means that there are going to be only a handful of viable browsers for KDE users (Konqueror/ReKonq, NetSurf and Midori) who aren't interested in EME/DRM (believe me, Mozilla won't get another cent from me, but KDE will!). Anyway, after searching, I found this rather old thread - viewtopic.php?f=27 ... 2&start=15 So my question is basically this: Is Konqueror going to be the default browser going forward, or is ReKonq the successor? Also, how do the KDE developers feel about the lack of non DRM'ed browser options that will soon be upon us? I really hope KDE can have a good HTML5 browser for those who don't care about Netflix and would prefer to stick with a fully open source browser, I just wondered how the KDE community at large feels about this.

*Also, in case anyone doesn't know what I'm referencing, I mean this - http://pando.com/2014/05/14/netflix-and ... dern-tech/ and this - http://blog.qupzilla.com/2014/03/new-bo ... ments.html

At the moment, Konqueror will continue to be the default web browser, as shipped by KDE upstream at least, for the remainder of the KDE 4.x series at least.

At this time it is too early to say what will happen with Plasma Next.

What about KHTML with KDE Frameworks 5? I was forced to compile (and still compiling) KHTML because Systemsettings (?!) but Qt has already build-in Webkit, which work pretty good (for Qt5 browsers can be used as reference Otter [1] ).

So, how KHTML will continue? At this moment, can someone point me to some advantage using KHTML over WebKit (in Qt) or Blink?

Thank you

[1] http://otter-browser.org/

One thing to note is that all Qt web browsers will have to switch to QtWebEngine (Blink from Chromium) since Qt WebKit has been put on ice.

So, the news that Qupzilla is switching to it are actually good. It will still be Qt, just with a more up-to-date fork (blink) of a fork (webkit) of khtml.

KHTML is a touchy subject. What will happen to it remains to be seen. As for the system settings, it should be tested which parts require it. If it is the module for configuring khtml, then ok, but otherwise I see no purpose in using any html renderer in the system settings.

System Settings uses KHTML for the Classic (Tree) View.