emulating document.docume ntElement on pre W3C DOM browsers

[Aaron Gray]

(Please tell me if this is silly or I am barking up the wrong tree)

Can someone check this please on pre W3C DOM browsers :-

function getDocumentRoot ()
{
for ( e in document.childN odes)
if ( document.childN odes[e].nodeName == "HTML")
return document.childN odes[e];
return document.body;
}

if (!document.docu mentElement)
document.docume ntElement = getDocumentRoot ();

There's an html test page here :-

http://www.aarongray.org/Test/JavaSc...ment-test.html

There's also a test for document.getEle mentById() emulation here :-

http://www.aarongray.org/Test/JavaSc...ById-test.html

Many thanks in advance,

Aaron

[Gregor Kofler]

SAM meinte:

Yes yes yes understood (while these missing {} are optional)

but with my "normal" way ...
30 lines to tell white spaces missing and wrong indentation
Without forgiving unknown variables

It says, that it will "hurt your feelings". ;-)

At first I was pretty pissed by the way JSLint was complaining about
everything, too. However, after spending quite some time tracking down a
bug due to an undeclared variable, I frequently check my scripts with
JSLint. You can still ignore the "error messages", once you know what
causes them.

Gregor
--
http://photo.gregorkofler.at ::: Landschafts- und Reisefotografie
http://web.gregorkofler.com ::: meine JS-Spielwiese
http://www.image2d.com ::: Bildagentur für den alpinen Raum

[SAM]

Gregor Kofler a écrit :

>
At first I was pretty pissed by the way JSLint was complaining about

(...)

You can still ignore the "error messages", once you know what causes them.

And finally, what's the use to continue to use it ?

--
sm