218

I believe that konqueror does not have any serious rendering problems anymore(except version 3.5.x)
KHTML must kontinue( ). What we really need is a better javascript behavior in general.

pembo13 wrote:Are you saying that Gmail doesn't work in Safari or Chrome?

Last time I checked, they did But I don't think that depends on webkit. It only means that Gmail checks specifically for Safari and Chrome respectively, while it does not check for Konqueror.

pembo13 wrote:Not the last few times I tried. Will try again. Every time I've tried, it simply does not work properly in Konqueror. Regardless of how poorly Gmail may be designed, it is usable in other browsers with full features.

Well, last time I checked I could use the features of Gmail that I wanted to with Konqueror (masquarding as Firefox). Still, only an example. Then again, most sites I've tried with works. The only three reasons I have for predominately using firefox are:

*It's faster
*It has a couple of extensions I rather like
*Moonlight doesn't work in Konqueror (which is required for some of my work-related issues).

A main blocker preventing Webkit from truly integrating with Konqueror is the fact that QtWebkit does not expose the DOM tree, which prevents things like KWallet, Popup blockers, etc. from functioning.

bcooksley wrote:A main blocker preventing Webkit from truly integrating with Konqueror is the fact that QtWebkit does not expose the DOM tree, which prevents things like KWallet, Popup blockers, etc. from functioning.

Well I would like to believe that Qt Software would be willing to fix that.

Kryten2X4B wrote:Last time I checked, they did But I don't think that depends on webkit. It only means that Gmail checks specifically for Safari and Chrome respectively, while it does not check for Konqueror.

Even if you change konqueror's user agent to something gmail accepts it still doesn't work properly.

TheBlackCat wrote:Even if you change konqueror's user agent to something gmail accepts it still doesn't work properly.

I just tried this out again, and as before, switching user agent makes "Standard" unusable.

Interesting note:

I just installed and tried Arora, it loads and works with Gmail with no changes by myself, and on the first try.

arkara wrote:I believe that konqueror does not have any serious rendering problems anymore(except version 3.5.x)
KHTML must kontinue( ). What we really need is a better javascript behavior in general.

KJS is just broken. I believe that there are so many quirks that there is no
change to fix them all. Even if they did, KJS is too slow compared against
Squirrelfish or V8.

Firefox was already bashed yesterday in the press for having a javascript
engine that is too slow. Even in the upcoming 3.5 Release. They compared
it with V8 from chrome.

I believe that there isn't enough manpower in the KDE Team to come up
with a kjs engine, that will be comparable to that.

So integrate V8 or Squirrelfish if possible and may be keep KHTML. KHTML
does a decent job in KDE 4.2.

Regarding KJS, I think it is better than firefox 3 ! In the peacekeeper benchmark I get these result:
firefox 3.0.7: 305
KHTML: 326

The main issue for me is lack support for WYSIWYG editors. You will be surprised if you know there are only three guys working in KHTML in their spare time:
Germain Garand
Vyacheslav Tokarev
Maksim Orlovich

Zayed wrote:Regarding KJS, I think it is better than firefox 3 ! In the peacekeeper benchmark I get these result:
firefox 3.0.7: 305
KHTML: 326

The main issue for me is lack support for WYSIWYG editors. You will be surprised if you know there are only three guys working in KHTML in their spare time:
Germain Garand
Vyacheslav Tokarev
Maksim Orlovich

This is not the point, we do not only need it fast, but we need it compatible as well
which is not

arkara wrote:

Zayed wrote:Regarding KJS, I think it is better than firefox 3 ! In the peacekeeper benchmark I get these result:
firefox 3.0.7: 305
KHTML: 326

The main issue for me is lack support for WYSIWYG editors. You will be surprised if you know there are only three guys working in KHTML in their spare time:
Germain Garand
Vyacheslav Tokarev
Maksim Orlovich

This is not the point, we do not only need it fast, but we need it compatible as well
which is not

I think the main problem is in the websites themselves. Right now KHTML scores 85 point in the Acid3 and 100% in Acid2.

Anyway, there is no manpower enough to improve the browsing experience in the KDE. This is the real problem.

f33l wrote:

TheBlackCat wrote:Someone is already working on a webkit plugin for konqueror and someone else is working on a separate dedicated webkit browser for KDE.

Glad to hear. I think KDE should make this a top priority.

Isn't Webkit the Apple fork of khtml?

Kadde wrote:

f33l wrote:

TheBlackCat wrote:Someone is already working on a webkit plugin for konqueror and someone else is working on a separate dedicated webkit browser for KDE.

Glad to hear. I think KDE should make this a top priority.

Isn't Webkit the Apple fork of khtml?

It is.... but under several licence (maybe two : LGPL - BSD)

Kadde wrote:

f33l wrote:

TheBlackCat wrote:Someone is already working on a webkit plugin for konqueror and someone else is working on a separate dedicated webkit browser for KDE.

Glad to hear. I think KDE should make this a top priority.

Isn't Webkit the Apple fork of khtml?

Yes, But there were some communication problems between Webkit and khtml developers for many years. Because of that, the merging back webkit to khtml is very difficult and very slow.

Bear in mind that webkit and khtml are just html engine only and not browser. To build a browser on top of webkit you need a lot of time and efforts. Right now, there are two browser only using webkit: Apple Safari and Google Chrome. Each of them is developed by a big company not by one guy !

Zayed wrote:I think the main problem is in the websites themselves. Right now KHTML scores 85 point in the Acid3 and 100% in Acid2.

Anyway, there is no manpower enough to improve the browsing experience in the KDE. This is the real problem.

Well blaming the websites is a cop out if more and more KHTML is the the only one that has so many problems.