[thelist] DOM - removeNode() problems

[Jeff Howden]

tom,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Tom Dell'Aringa
>
> Ahh, well then I misread my source. Still odd that after
> I removed it, I could alert it as an object.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

agreed, but i'm sure there's some explanation for that.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > first, and simplest, you can set the innerHTML of your
> > error <div> to an empty string.
>
> Yeah, while easy I want to avoid it since its not the
> DOM.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

well, i'd give that reason a big, fat *whatever*.  ;p

i seem to recall just a few months ago you were trying to find reasons to
use non-dom0 ways to access forms and form elements.  considering the level
of support for innerHTML, what exactly is your reasoning here again?

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> I like 2 and 3 the best, I'll try those. Thanks jeff.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

what strikes me as funny is that both methods are practically identical.
it's too bad there's not a removeChildNodes() method that would clear out
all children of an object in one method call.

.jeff

------------------------------------------------------
Jeff Howden - Web Application Specialist
Resume - http://jeffhowden.com/about/resume/
Code Library - http://evolt.jeffhowden.com/jeff/code/