Saturday 10 February 2001 12:36, �� ��������:
| The one weakness of Konqueror, is?
|
| You guessed it; Javascript. Reference this quote:
|
| "Konqueror HTML 4 Compatibility Results
| http://www.bsdtoday.com/2000/November/Features339.html
| I used the i-Bench benchmark from Ziff Davis to test Konqueror's HTML 4
| compatibility. My results show Konqueror passing or partially passing 98
| of the 133 tests. Of the tests that Konqueror didn't pass, most of them
| dealt with table and text alignment, border styles and JavaScript events.
| Konqueror also passed all of the graphics tests except for animated GIFs.
Raymond,
This is mostlly correct for early release.
Taking into consideration with which Konqueror develops it's like to say that
MS IE 2.0 was not able to complete Netscape navigator tests.
Yes, it was, but it was ome time ago.
I guess (it's my personal estimation, as I monitor KDE project for some time
already) that KDE's development speed is 3 (three) times faster then
Microsoft's speed.
And, I think by the time Witzler (Windows XP) ready, together with MS IE 6.0
(I hardly believe in MS's promises that it will happen in Autumn 2001),
Konquerror will outperform MS IE on all W3C standard compliance tests.
BTW: how many of these 133 tests MS IE and Mozilla (NS6) passed?
I guess not much more.
If they passed much more, then the tests are wrong (bad)
Just look at my HTMLtests page at http://htmltests.newmail.ru to know why.
Re:
| Konqueror did run into a few problems with some other i-Bench tests: it
| crashed on the WAV sound file test and locked up my system during the
| JavaScript stress test."
I have 2 testcases where MS IE repeatably crashes.
It is W3C HTML 4.0 valid code.
And what?
You still use MS IE as benchmark.
I have testcases where Mozilla (NS6) repeatably crashes (ohh, yes, I forgot
that you don't take NS6/Mozilla seriously)
And, for your information, such crashes (like on WAV file) were fixed already
in November.
Konqueror now plays not only WAV, but Flash and other plugin-supported media
formats, easily picking up installed Netscape Navigator plugins.
You even don't need to run special install program for this.
| I've read about this issue in a few places before. I think we need to
| wait til Konqueror reviews with passing scores in the area the DynAPI
| relies on almost 100%; Javascript.
Yes, exactly. You need to wait for this Monday, Feb12th, or even few days
more, as KDE 2.1 will be released next week. :-))
|
| Laters
|
Now some more details from my analysis of DynAPI library.
I am seriously concerned with this fragment, for example:
// loadpanel.js
LoadPanel.prototype.insertInlineElements = function() {
if (is.ns4 && this.isILayer) {
this.setHTML('<ilayer></ilayer>');
}
else {
if (is.ie5) this.setHTML('<DIV ID="'+this.id+'loadElement"
STYLE="behavior:url(#default#download)" style="display: none;"></DIV>');
if (is.ie4) {
if (this.useBuffer) {
this.setHTML('<IFRAME ID="'+this.id+'loadElement"
STYLE="visibility:
hidden; display: none;" onLoad="LoadQueue.loadHandler()"></IFRAME>');
}
else {
this.setHTML('<IFRAME ID="'+this.id+'loadElement"
WIDTH="+this.getWidth()+" HEIGHT="+this.getHeight()+" STYLE="visibility:
hidden; display: none;" onLoad="LoadQueue.loadHandler()"></IFRAME>');
}
}
}
};
---------------------------------------------------------------
If you were testing like :
--------------
if (is.DOM) { .....}
else
if (is.ns4 && this.isILayer) { .. }
else if (is.ie5) { ...}
else if (is.ie4) { ...}
--------------
then it's ok with me.
But you are not giving Konqueror here a chance, as it is:
-not MS IE
-not NN
according to your browser detection code. (see my yesterday's mail about this)
If you change browser.js to
IE4up = (document.all) ? true : false;
DOM = (document.createElement ) ? true : false;
then it's ok with me (and Konqueror)
Konqueror will be recognized as both MS IE4.x or newer and DOM-compliant
browser in such case. And, most probably, will work ib both modes as well.
BTW: I don't want to see test like if ( is.Konqueror ) or if (is.Opera).
If ( is.DOM ) is enough, and should cover all DOM-compliant browsers.
Besides, I guess
instead of
------
setHTML('<DIV ID="'+...
much better to use:
------
el = document.createElement("DIV");
el.id = this.id;
...
this.appendChild = el;
or something like taht.
Or you don't agree here?
(but as I have seen in setHTML implementatiom, it uses innerHTML method after
all, so it should work with Konqueror as well.)
These constructions are all supported by Konqueror, and can be used
successfuly for creating and manipulating DIV tags.
innerHTML is also supported.
IFRAME supported - as well.
So, DOM structure is here, DIV and IFRAME are here, question is if it is
allowed Konqueror to be recognized in browser.js?
Another fragment I am concerned is:
dynlayer.js
--------------------
else if (is.ns5) {
while (this.elm.hasChildNodes())
this.elm.removeChild(this.elm.firstChild);
var r=this.elm.ownerDocument.createRange();
r.selectNodeContents(this.elm);
r.collapse(true);
var df=r.createContextualFragment(html);
this.elm.appendChild(df);
for (var i in this.doc.images) this.doc.images[i].lyrobj=this.elm;
------------------------------
It's not very clear for me what you are doing in this code, but most likely
it has toi be rewritten for Konqueror. I am wondering if fragment above cab
be run in MS IE 5. Most likely, not as you check for ns5 above.
I am cc'ing Harri Porten who is maintainer for Konqueror's JavaScript (to be
precise, ECMAscript) implementation. May be, he can comment on this code when
he has some time.
As I already mentioned, major KDE upogrdae, version 2.1, is expected in few
days, so everybody is quite busy doing bug fixing and final polishing.
--
Vadim Plessky
http://kde2.newmail.ru (English)
http://kde2.newmail.ru/index_rus.html (Russian)
Do you have Arial font installed? Just test it!
http://kde2.newmail.ru/font_test_arial.html
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
