Message: previous - next
Month: November 2011

Re: [trinity-devel] Konqueror Web Browser.

From: "Richard J.M. Hill" <cycledaemon@...>
Date: Sat, 19 Nov 2011 18:20:44 -0500
On Saturday 19 November 2011, Timothy Pearson wrote:

> Just as a note, this really is a distribution packaging issue.  The KHTML
> engine is already fairly well split within kdelibs, and if an external
> renderer is used in the future then updates will be split by default.
> Tim

You raise a good point; and while I agree that any external
rendering-engine which may be used by Konqueror will receive
updates from its parent organization (or from Linux distribution
maintainers), I think that the availability of KHTML as the default
renderer is a bad idea (especially for non-technical users who may be
unaware of the implications of using it).  It would be better, in my
opinion, if when Konqueror is first started, it were to prompt the user
to select one of Gecko, Webkit, etc. to use for web browsing.  Maybe
it could also present a warning as to the danger of using KHTML due
to the lack of security updates.



Stupidity is its own reward.