jQuery is supposed to simplify things, not force the user to shove ugly
native DOM code into something programmed in jQuery.
You're suggesting instead of creating a simple .detach() method, we
force programmers to type in
$('.someMultiNodeSelector').each(function()
{this.parentNode.removeChild(this);}); ? I honestly think
$('.someMultiNodeSelector').detach(); makes more sense.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com]
-Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com)
-MonkeyScript (http://monkeyscript.org)
-Animepedia (http://anime.wikia.com)
-Narutopedia (http://naruto.wikia.com)
-Soul Eater Wiki (http://souleater.wikia.com)
Matt Kruse wrote:
> On Feb 25, 5:46 pm, Már Örlygsson <[email protected]> wrote:
>
>> Thus we'd have two quite unambiguously named methods - `.destroy()`
>> and `.detach()` - with no nasty surprises attached. :-)
>>
>
> But why do you need another jQuery method just to call
> parentNode.removeChild?
> The .remove() method handles all the jQuery internals, as a jQuery
> method should.
> If you just want to remove an object from the DOM, just use simple,
> standard javascript.
>
> Matt Kruse
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
