Site compatibility for Firefox 3

In Gecko 1.8, it was not possible to set capturing load event listeners on images. In Gecko 1.9, this has been fixed by Webkit bug 234455. But this can cause problems on websites that incorrectly have their event listeners set to capture the load event. See the discussion in Webkit bug 335251. To fix this problem, the problematic page in question should not set a capturing load event listener.

For example, this:

window.addEventListener('load', yourFunction, true);

should be changed into this:

window.addEventListener('load', yourFunction, false);

For an explanation of how event capture works, see DOM Level 2 Event capture

In Gecko 1.8, the preventBubble method existed on events to prevent events from bubbling upwards. In Gecko 1.9 this method has been removed. Instead, you should use the standard stopPropagation(), which also works fine in Gecko 1.8. The patch in Webkit bug 330494 made this happen. See also Webkit bug 105280.

window.captureEvents, window.releaseEvents and window.routeEvent are now considered deprecated since Gecko 1.9.

Nodes from external documents should be cloned using document.importNode() (or adopted using document.adoptNode()) before they can be inserted into the current document. For more on the Node.ownerDocument issues, see the W3C DOM FAQ.

Firefox doesn't currently enforce this rule (it did for a while during the development of Firefox 3, but too many sites break when this rule is enforced). We encourage Web developers to fix their code to follow this rule for improved future compatibility.

In Gecko 1.8 the function intersectsNode code be used to test if a node intersected a range. However the return values from this function were confusing and rarely useful and has therefore been removed in Gecko 1.9. Instead use the more precise and standard function compareBoundaryPoints. The patch in Webkit bug 358073 removed this function.

See the documentation for intersectsNode for how to use compareBoundaryPoints instead.

In Gecko 1.8 the function compareNode code be used to test how a node intersected a range. However the return values from this function were confusing and rarely useful and has therefore been removed in Gecko 1.9. Instead use the more precise and standard function compareBoundaryPoints. The patch in Webkit bug 358073 removed this function.

See the documentation for compareNode for how to use compareBoundaryPoints instead.

object and embed elements no longer need a type attribute to render. Changing the src attribute (of <embed>) or the data attribute (of <object>) via JavaScript now works correctly. The Content-Type header sent by the server (if any) now takes precedence over the type attribute of an <object> element as per the HTML specification (this is not the case for embed).