Martin Kadlec blogging

DOM3 Core implementation

Nowadays lots of developers are talking about HTML5 and CSS3. A bit fewer of them are talking about ES5 (EcmaScript5). But it looks like most of them nearly forgot the DOM3 specification and I don't think it's right because DOM3 implementation in browsers is really poor and should improve. That is why I created the DOM 3 Core implementation test. In future I want to add more parts of DOM3 like "DOM3 Events", "DOM3 XPath", "DOM3 Load and Save" etc.

Anyway, in the latest Opera build (9044) Opera implemented CustomEvents and few other things from DOM3 so there is hope that there will be more in the near future.

So if you are interested what your browser can do from DOM3 go here:

Please login to post comments.
19.12.2010 07:12
True, although that specification is getting to be about the size of the Tower of Babel. It would be nice if some of its features were split out such as the Window object (again).
19.12.2010 04:12
Personally I would like to see the DOM0 events normatively specified out more than DOM3 Load and Save support. With previously proprietary events like innerHTML being standardized, the pressing need for DOM3 diminishes somewhat.

Hallvord discussed the DOM0 problem in and in this thread,
19.12.2010 04:12

Originally posted by Turin:

Personally I would like to see the DOM0 events normatively specified

They are in HTML5, are they not?
13.09.2010 15:09
Interesting fact:
Prototypes of native objects in Opera don't know properties, they only have constants or methods. So "any property that is defined by spec on any prototype X" in "Prototype X" = false

That's why in the test the "documentURI" property looks like Opera doesn't support it
12.09.2010 01:09
I think one of the main reasons behind this disinterest could be the return to love of HTML (the originally SGML based language), and the standardisation of a lot of APIs previously popularly considered "hackish".

DOM was designed to manipulate XML documents, and as such only really suited the "model" when XHTML was being popularised. It's somewhat lost it's sheen of late - most people aren't even aware there's an XML serialisation in the HTML5 spec. - so in the absence of a popular XML-based format for the web, DOM is a lot less relevant.

I'm not sure what will happen once IE9 comes out with all its SVG support - which will necessitate DOM manipulation big-time I think.