Firefox and the DOM

Firefox is very conscientious about whitespace - it often (if not always) creates a separate text node for whitespace, rather than ignoring it. It's as if its rule is 'not even whitespace must be thrown away'. This means that you cannot assume that, for example, a TR node's nextSibling will be the next TR in the table. It may well be a whitespace text node - one which will be invisible when you inspect the structure, too. So if your scripts don't find the siblings they expect, put in a loop to seek the next non-text node sibling (or parent, or child etc etc).