On Thu, 06 Apr 2017 07:46:40 +0200 deloptes <deloptes@xxxxxxxxx> wrote: > Jan Kleks wrote: > > > 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. 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. E. Liddell --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
