6 Apr
2017
6 Apr
'17
1:03 p.m.
On Thu, 6 Apr 2017, Jan Kleks wrote:
2017-04-06 13:48 GMT+02:00 E. Liddell
<ejlddll(a)googlemail.com>om>:
I use konqueror foremost as a file manager _between_ systems (sftp://...)
AND as an old browser to check my web pages to insure they play nice
when visited by someone using an older browser.
I don't doubt that others do, too.
Jonesy
--
Marvin L Jones | Marvin | W3DHJ | linux
Pueblo, Colorado | @ | Jonesy | FreeBSD __
38.238N 104.547W | jonz.net | DM78rf | OS/2 SK
On Thu, 06 Apr 2017 07:46:40 deloptes
<deloptes(a)gmail.com> wrote:
Apart from Webkit there is also QtWebEngine used, for instance, by Otter
Browser (
http://browsingthenet.blogspot.com/2016/03/k-meleon-vs-qupzilla-vs-otter-br…).
This engine might be worth considering as well.
An alternative to replacing the rendering engine would be to remove
Konqueror's web capabilities altogether (what's the point of have a broken
browser?), and adopting another lightweight browser for the TDE (or just
removing Konqueror and leaving the matter of installing their favorite
browser to the users).
For the time being, when launching Konqueror for the first time it could
show a message that web rendering is broken for now, and the TDE Team
suggest installing another browser. So that the users won't think that the
TDE is outdated or something because of this. Jan Kleks wrote:
Improving KHTML isn't in the cards, I don't think. Previous discussions
have focussed around porting the entire browser to a new rendering engine
(generally KHTML's descendant Webkit) that already supports the missing
CSS3 and HTML5 features. There's just never been enough manpower to
do the work.
The Javascript engine probably also needs to be updated. I don't know
how susceptible it is to piecemeal upgrades, as opposed to dropping the
entire thing and adopting something written for another browser.
I think this is a very important issue. Maybe a
bug-tracker ticket
should be created for discussing possible solutions?
I think we've already discussed it. My impression is that at the end it
comes to man power. With only few developers it's not possible to do
implement something better.
I suggest you discuss the topic on the dev thread. Perhaps we can make a
roadmap or something and slowly improve some aspects.