Uhm, you see `.detach()` is already on the 1.4 Roadmap. I've repeatedly seen developers getting burned by the assumtion that .remove() is somehow similar to the DOM method .removeChild() which makes the case *for* adding .detach() simple: there's obvious demand for it.
However, I'm derailing a bit... what I was trying to get flying was the idea of renaming of `.remove() ` to `.destroy()`, to remove the last trace of confusion with .removeChild() Does anybody have an opinion on that? -- Már Örlygsson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
