I did the W3C DOM tests in Mozilla 1.75 and Opera 8b and updated the tables. Mozilla doesn't show much progress (then again, it doesn't have to show much, it's already the browser that supports the W3C DOM best). Opera is on the move again.
See the Core, HTML, CSS, and Events tables.
The only minor problem I have with Mozilla is that it still doesn't support non-standard but very useful methods and properties like children[] and contains() which all other browsers support.
As to Opera, its programmers have clearly been busy:
getElementsByTagName('PPK') is now supported (ie: on custom tags)sourceIndex, a useful Microsoft extension, is supportedhasAttribute() is supported correctly.value of attributes is supported completely.button property. Instead it supports the W3C standard.removeAttribute() and timeStamp seem to be gone. Then again, I'm testing a beta, so maybe they will reappear in the final version.This is the blog of Peter-Paul Koch, mobile platform strategist, consultant, and trainer.
You can also follow
him on Twitter.
Atom
RSS
I’m around at the following conferences:
Categories:
Monthlies:
Comments are closed.
2 Posted by TarquinWJ on 1 February 2005 | Permalink
The next version of Safari should be 2.0, and will be shipped with OS X 10.4 Tiger. I have a preview copy of it, and I have to say, although its scripting speed has dramatically improved (from being one of the slowest browsers to being one of the fastest - http://www.howtocreate.co.uk/browserSpeed.html ), there is very little else that has changed.
However, it is, of course, a preview, and I know that there should be more fixes before the final release (some time in the first half of this year - apparently).
1 Posted by TWW on 25 January 2005 | Permalink
Wow. That's really very useful. Here's hoping the Safari team have some fixes lined up for the DOM in 1.3.