If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Enjoy an ad free experience by logging in. Not a member yet? Register.

The computer is always right. The computer is always right. The computer is always right. Take it from someone who has programmed for over ten years: not once has the computational mechanism of the machine malfunctioned.

The computer is always right. The computer is always right. The computer is always right. Take it from someone who has programmed for over ten years: not once has the computational mechanism of the machine malfunctioned.

The computer is always right. The computer is always right. The computer is always right. Take it from someone who has programmed for over ten years: not once has the computational mechanism of the machine malfunctioned.

this tells us that rowObj is not a row object (that would show [object HTMLTableRowElement]), but a Text Node (part of the DOM interface). Text Nodes do not have a .cells property (returning undefined) and calling [0] on undefined throws an error.

the problem is that the .firstChild call in IE has lately been fixed to match the behaviour of all other browsers (whitespace between elements counts as a separate text node, while IE has been discarding that for certain elements). if supported, use the .firstElementChild call (or make a workaround for it (e.g.) going through .childNodes until you hit an element child).

The computer is always right. The computer is always right. The computer is always right. Take it from someone who has programmed for over ten years: not once has the computational mechanism of the machine malfunctioned.