Mozilla, written html and getElementById

Richard A. DeVenezia · Sep 10, 2003

Mozilla (1.4 win2k) doesn't like this

document.write ('<TABLE ID="abc"><TR><TD></TD></TR></TABLE>')
table = document.getElementById ('abc')
alert (table.rows.length)

I see in JS Console, Error: table has no properties

The same message that would appear if I tried to get real non-existant id
table = document.getElementById ('abc-doesnotexist')
alert (table.rows.length)

Any work arounds ( Not in a position to place my own null table in source
HTML

) ?
Should I skip making 1.4 happy and wait for Moz 1.5+ ?

Richard A. DeVenezia · Sep 10, 2003

Richard A. DeVenezia said:
Mozilla (1.4 win2k) doesn't like this

document.write ('<TABLE ID="abc"><TR><TD></TD></TR></TABLE>')
table = document.getElementById ('abc')
alert (table.rows.length)

I see in JS Console, Error: table has no properties

This happens in a js that is being loaded in the <HEAD> tag

Richard Cornford · Sep 10, 2003

Richard A. DeVenezia said:
This happens in a js that is being loaded in the <HEAD> tag

A table element within the HEAD of a document would be invalid so if the
function is called within the head it is unrealistic to expect it to
work. But I would be expect timing problems with this code anyway as
the browser may not get a chance to fully set up the objects created
with the document.write statement before it is references. (Indeed I
recall that at least one browser delays document.write output until the
completion of the current script block)

It would probably be safer to use DOM node insertion methods to create
and insert a valid table structure. Then you would have a reference to
it prior to inserting it and would not have to use getElementById at all
(or give the table an ID). Alternatively you would probably have to
split the code with the document.write inserting the HTML inline and
another "init" function being called onload (or with a timeout).

Richard.

Lasse Reichstein Nielsen · Sep 10, 2003

My guess:
You use document.write to insert context in the input stream after
the current script element. It is not parsed until after the script
tag ends.

Try ending the script tag after the document.write and start a new
script tag with the rest of the code.

This happens in a js that is being loaded in the <HEAD> tag

So, you are writing tables into the head tag? That means that
the head tag must have stopped, so the browser automatically ends
the head tag and starts the body tag.

/L

Gavino Paolini · Sep 10, 2003

Il Wed, 10 Sep 2003 11:32:52 +0200, Lasse Reichstein Nielsen ha scritto:

....
So, you are writing tables into the head tag? That means that the head
tag must have stopped, so the browser automatically ends the head tag
and starts the body tag.

/L

Maybe he meant that the script tag containing that portion of code is
inside the head and not in the body, I'm just supposing.

gp

getElementById returns null	6	Jan 25, 2009
getElementById and Firefox	4	May 24, 2006
Image opacity flicker and getElementById	1	May 2, 2006
GetElementByID nog working for DIVs in Firefox?	1	Jul 19, 2006
Help with my responsive home page	2	Dec 14, 2022
Load Body html on button click.	3	Sep 29, 2008
Moving dynamically created table rows up and down in an HTML table	2	Oct 10, 2008
Onblur not working in mozilla, fine in IE	3	Jan 15, 2007

Mozilla, written html and getElementById

Richard A. DeVenezia

Richard A. DeVenezia

Richard Cornford

Lasse Reichstein Nielsen

Gavino Paolini

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads