Description of problem: Konqueror uses KHTML by default, KHTML is *very much* slower, and less HTML5 compatible than WebKit, Konqueror can use WebKit by installing kwebkitpart, I think we should ship it as Knoqueror default. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Personally I think we should stick with upstream on this, but I'll leave that up to the KDE team to decide.
CC: sysadmin-bugs => mageiaComponent: Release (media or process) => RPM PackagesAssignee: bugsquad => lmenut
(In reply to David Walser from comment #1) > Personally I think we should stick with upstream on this, but I'll leave > that up to the KDE team to decide. I think there is no active develpment upstream, KHTML is several times slower (in JavaScript, I tried Kraken, but it didn't finish at all using KHTML, using sunspider, KHTML 2636 vs WebKit 167 on my laptop, more than 15x), and less HTML5 compilent (about 103 vs 407 out of 555 in html5test.com) Regards Mustafa
(In reply to David Walser from comment #1) > Personally I think we should stick with upstream on this, but I'll leave > that up to the KDE team to decide. I prefer to follow upstream choice too. (In reply to Mustafa Muhammad from comment #2) > I think there is no active develpment upstream, KHTML is several times > slower (in JavaScript, I tried Kraken, but it didn't finish at all using > KHTML, using sunspider, KHTML 2636 vs WebKit 167 on my laptop, more than > 15x), and less HTML5 compilent (about 103 vs 407 out of 555 in html5test.com) Feel free to convince upstream Konqueror maintainer to use WebKit by default instead of KHTML.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX