On Saturday 19 November 2011, Richard J.M. Hill
wrote:
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.
Richard.
Konqueror has too many perks to give up as a web browser, superior
tabbing,
panels, profiles and more. I really think its best to change khtml to
another
engine or see what MAC as done with it. Remember, Safari was khtml, so it
can
be done. Yes, I know MAC is a billion dollar business, but still.
Kate
PS Tim, where can I change the email addy these mailings are sent to. I'd
like
to keep my personal email clean of devel stuff. With all the projects, its
too much. So I created some more emails for this use. Thanks.
The best way is to unsubscribe your old address and then re-subscribe via
your new address.
Tim