Known Issues for Mozile 0.8 General Internet Explorer 2006-04-09: IE won't let your overwrite the global "document" object. 2006-04-10: IE's selectNode and selectSingleNode methods only work inside XML documents. 2006-04-10: mozile.xpath.getXPath(Attr) doesn't work because Attr.parentNode and Attr.ownerElement don't seem to work. 2006-04-10: XPath code is still buggy for IE in XML pages. So in test/core/xpath.js the testGetXPath function skips this case. 2006-04-21: IE doesn't support getAttributeNS/getAttributeNodeNS, so you have to use getAttribute/getAttributeNode with the full qualified name. 2006-04-21: IE doesn't support createElementNS, so use mozile.dom.createElementNS. 2006-04-23: IE doesn't support Element.hasAttribute(). 2006-04-30: IE's selection.createRange() behaves very badly when it is collapsed and not inside a contentEditable area. 2006-05-10: IE doesn't (always?) count white-space text nodes as actually existing. 2006-06-09: IE's Element.getAttribute("style") returns the style object and not the style attribute value. Try getting and setting Element.style.cssText instead. 2006-06-24: IE's Element.getAttribute("class") doesn't work. Use Element.className instead. 2006-07-11: When creating a table using JavaScript, IE wants you to include a
element. Safari 2006-04-10: Safari doesn't like the XML test pages, so for that browser the testsuite skips the XML tests. 2006-01-12: Strange bug with XML documents generated using mozile.xml.parse. When an RNG schema is created from the XML, it can cause a browser crash by accessing the _childNodes array. Doesn't seem to affect documents loaded from an external file. Perhaps related to: http://www.jtauber.com/blog/2006/03/09/crashing_safari http://www.opendarwin.org/pipermail/webkit-dev/2005-June/000112.html This is fixed in the WebKit nightlies avbailable at http://webkit.opendarwin.org/ 2006-04-21: Safari has inadequate XML namespace support. Attributes such as "xmlns:a" are changed to "a", which destroys their meaning. 2006-04-21: Safari's DOMParser gives elements the XHTML namespace when no "xmlns" attribute is given. 2006-04-22: Safari's document.createElementNS() method uppercases the element, like in HTML. This makes it useless for creating XML elements. 2006-04-25: Safari has a very smll JavaScript call stack (~100 calls versus ~1000 on Mozilla). This means that when validating XHTML with a depth of 6 node or more, there may be an error such as "RangeError: Maximum call stack size exceeded.". No workaround at this time. See http://bugzilla.opendarwin.org/show_bug.cgi?id=4045 2006-06-24: The getElementById() method doesn't work properly in XML unless there is a DTD defining IDs. Mozilla 1.7 2006-04-09: Old Mozilla versions mess up identity checks for attribute nodes. Comparing nodeNames instead should work well enough. 2006-04-24: Old Mozilla versions can hang on bad MIME types for XMODocument.load(). THis is big trouble for loading ".rng" files. Instead use XMLHTTPRequest and the overrideMimeType("text/xml") method. Firefox 1.5 (and likely older versions of Mozilla) 2006-06-26: designMode breaks window.onbeforeunload 2006-07-07: The event.rangeParent and event.rangeOffset for dblclick events inside hyperlinks are often wrong. For text nodes after the first, the rangeParent is the first text node, and the offset is the length of the rangeOffset. This doesn't seem to be a problem with other mouse events. Opera 9.0p2 2006-04-23: Opera's Element.lookupNamespaceURI() method only checks the current element and not its ancestors (unlike Firefox). So write your own loop for climbing the DOM tree. 2006-04-24: Opera doesn't pass the XPath XML tests yet. 2006-04-24: Opera gratuitously adds a "shape" attribute to HTML "a" elements, even when none is specified. For this reason mozile.dom.isIgnored() ignores "shape" attributes for links when Opera is detected.