This sounds like a good candidate for event delegation. I believe that jQuery.fn.live implements this for bubbling DOM events: http://docs.jquery.com/Events/live#typefn.
On Mon, Mar 30, 2009 at 9:04 AM, Már Örlygsson <[email protected]>wrote: > > > I believe this is a bug. Is there a workaround/fix tet? > > It's intended as a feature. > Most jQuery newcomers must find out the hard way that .remove() is > really more like a "destroy" or "delete" method. > If you .remove() an element you're signalling that you don't intend to > use it again. > > Fortunately there seems to be a "detach" method on the jQuery > development road map (http://docs.jquery.com/JQuery_1.4_Roadmap#DOM) > which will do what you need. > > Until then you'll need to roll your own.. > > jQuery.fn.detach = function(){ > return this.each(function(){ this.parentNode.removeChild(this); }); > } > > > > -- > Már > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
