View Full Version : DOM Level 2 Support
Does anyone know which IE and NN browser versions began to support DOM Level 2?
Thanks for your help.
I think IE 6 and higher and NS 6 and higher
Some of teh DOM 2 are supported by IE 5.5 also, but i think there is not a full implementation.
IE does not support any module of DOM2 at all. It supports DOM1 HTML and DOM1 XML. Some parts of that carry over into DOM2 Core and DOM2 HTML, but that doesn't mean it really supports those modules.
DOM1 HTML, DOM1 XML, DOM2 Core, DOM2 HTML, DOM2 Traversal, DOM2 Range, DOM2 Stylesheets, DOM2 CSS, DOM2 Events, DOM2 Views, and DOM3 XPath.
Opera 7 supports:
DOM1 HTML, DOM1 XML, DOM2 Core, DOM2 HTML, a little of DOM2 CSS, DOM2 Views, and DOM2 Events.
Thank you for your replys.
06-04-2003, 08:20 PM
JKD - You forgot [DOM3 LS] for Mozilla, which also MSXML in ie has part support for (not much, basically only an extended version of DocumentLS, but it's there. Note that the DOM wasn't the original source for the ideas that are implemented, however. Microsoft invented it and Mozilla jumped on the train, and then W3C kinda had to give in...).
As a detail, it should be [DOM1 Core] and not [DOM1 XML].
KHTML (Konqueror, Safari, possibly OmniWeb4.5+):
[DOM1 Core], [DOM1 HTML], [DOM2 Core], [DOM2 HTML], [DOM2 Views], [DOM2 Events], [DOM2 TR] (containing [DOM2 Transversal] and [DOM2 Range]), and most of [DOM2 Style] (containing [DOM2 StyleSheets] and [DOM2 CSS]). I believe [DOM3 LS] is being worked on together with the dynamic XML handling support for the moment, so that shouldn't be too far away.
Mozilla implements DocumentLS.load()... that's about it (AFAIK). The Load & Save specification was in Working Draft phase last I looked, so you really can't claim compliance to a standard that is still being modified.
Mozilla does implement XMLSeriailizer() and DOMParser(), whose functionality are equivalent to certain parts of DOM3 L&S. but those methods certainly don't exist in the specs.
06-04-2003, 10:20 PM
Have a look at <http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/hierarchy.html> to see that DOMBuilder etc. also are there. Have a look at DOMWriterFilter (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfaceDOMWriterFilter.html), DOMWriter (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDOMWriter.html), DOMBuilder (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDOMBuilder.html), DOMBuilderFilter (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDOMBuilderFilter.html), DOMInputSource (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDOMInputSource.html), DOMImplementationLS (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDOMImplementationLS.html), DOMEntityResolver (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDOMEntityResolver.html), LSLoadEvent (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMLSLoadEvent.html), LSProgressEvent (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMLSProgressEvent.html), and the optional DocumentLS (http://unstable.elemental.com/mozilla/build/latest/mozilla/dom/dox/interfacensIDOMDocumentLS.html). They only lack the optional convenience feature ElementLS. This high level of compliancy is kinda natural, since it's mozillan JST that is the Editor of this module.
I think I can agree with you that since it's not a CR, PR, REC or standard, you can't really claim conformance to it, though. But they have it in the engine.'
Yay - my first post to this forum from a mac!
typeof document.implementation.createDOMBuilder == "undefined"
When I check it out (build id 2003050811).
Unless the files were checked in recently (doubtful, pretty sure there I would have seen an announcement about a DOM3 L&S implementation), they are simply just there. If you'll look at the DOM interfaces that KHTML has, you'll find a bunch of stuff that just simply isn't implemented, similar to this.
06-04-2003, 10:41 PM
Oh, but this is implemented. In XUL you can use it. It's just that document.implementation in html rendering mode uses nsIDOMDOMImplementation instead of NSIDOMDOMImplementationLS. I don't know about SVG or XML rendering modes.
I'm getting undefined in XMLDocument and XULDocument as well.
I think it's about time I updated my nightly anyway...
Alright, 2003060209 GDI+ build.
document.implementation.createDOMBuilder and window.DOMBuilder are both undefined within instances of HTMLDocument, XMLDocument, and XULDocument.
See here: http://bugzilla.mozilla.org/show_bug.cgi?id=155749
06-05-2003, 12:00 AM
Talked a bit on #mozillazine, and got to know that it's in the build, there's just nothign that uses it yet :-( Not even XUL. Seems they have to fix a few implementation issues before it's good enough to use.
Powered by vBulletin® Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved.