Using native IE method (swapNode) might help for weird issues in table. http://msdn.microsoft.com/en-us/library/ms536774(VS.85).aspx
if (element.swapNode) return element.swapNode(secondElement); 2008/9/23 EMoreth <[EMAIL PROTECTED]> > > Shouldnt it use the parent node of both elements ?? > > Cause if i decide to swap 'div1' and 'div2' here ill have no > nextSibling (assuming that no textNodes would be returned as > siblings)... > > <div> > <div> > <div id="div1"></div> > </div> > <div> > <div id="div2"></div> > </div> > </div> > > > EMoreth > On Sep 23, 5:04 pm, kangax <[EMAIL PROTECTED]> wrote: > > On Sep 23, 11:25 am, John-David Dalton <[EMAIL PROTECTED]> > > wrote: > > > > > @Tag can you provide a case where this would be a real issue ? > > > I can't see someone swapping nodes with the document.documentElement > > > or anything. > > > > I think `Element.replace` is a good way to ensure no cross-browser > > bugs crawl in (aren't there glitches with `insertBefore`, table > > elements and IE?) > > > > -- > > kangax > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
