JDD, didn't want to rise extra issues, your code and the lazy initialization are perfect and fast, but if I remember correctly I preferred to leave out native IE "swapNode" because it was impossible to do swaps between DOM nodes of different contexts (documents), but I may recall it wrong !
In that case, should that kind of test be in the test unit ? As said above, using native IE "swapNodes" may cure some IE weirdness with tables, but I have no knowledge of such problems with insertBefore and tables ! It is correct the catch about cases where there are no "nextSibling". The inserBefore will then behave as appendChild as you said. These cases should be part of the test unit. -- Diego Perini On 24 Set, 07:17, John-David Dalton <[EMAIL PROTECTED]> wrote: > @Kangax > I am not aware of any issues with insertBefore and table elements. I > know that IE has issues with innerHTML and table/select elements. > > @EMoreth > if nextSibling is null insertBefore will act as appendChild so it > should still work out.http://developer.mozilla.org/en/DOM/element.insertBefore > > @Simon > Here is my patch uses a 1 time check to fork for browsers that support > swapNode.http://prototype.lighthouseapp.com/projects/8886/tickets/351-new-swap... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to email@example.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 -~----------~----~----~----~------~----~------~--~---