On another note... if the element you want to remove is also created
by javascript, why don't you store the reference somewhere and remove
that way?
what happens if you use prototype's own remove() method?
// $('img1').remove()
greetz,
Wizz
On 26 nov, 17:26, Wizz <[EMAIL PROTECTED]> wrote:
> Not sure if I'm correct, but what would be the significance of
> 'unextending' an object if you're going to remove it anyway? That's
> like... cleaning your car before you drop it into the crusher. 8/
>
> On 25 nov, 04:13, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > Is there a way to unextend an extended object?
>
> > For example, I have the following code that is causing a memory leak
> > in IE6....
>
> > var myImg = document.createElement('img');
> > myImg.id = 'img1';
> > document.body.appendChild(myImg);
> > ...
>
> > var delImg = $("img1");
> > delImg.parentNode.removeChild(delImg);
> > ...
>
> > but if I use getElementById, its okay...
> > var delImg = document.getElementById("img1");
> > delImg.parentNode.removeChild(delImg);
>
> > After removing, if I can unextend delImg, then IE6 should be able to
> > cleanup the memory.
>
> > thanks,
> > dat.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
