Walter, Element constructor shouldn't really care if there's an element with the same id. Inserting those elements into the DOM is what matters. On the other hand, I won't be surprised if IE has some glitches about this. What exactly doesn't work when you replace an element with the one that has the same id?
- kangax On Apr 20, 1:44 pm, Walter Lee Davis <[EMAIL PROTECTED]> wrote: > Yay! That works. Now one last question. > > In my fumbling around trying to make it work, I went down this road > of thought: > > Maybe the "new Element" stuff doesn't like to create a new object > that has the same ID as another object already in the DOM. So I added > this little _t to the end of the substituted field ID. > > Is this really necessary? Or is it handled by the replace() function? > If I build up a new element ( and I moved my element creation out of > the replace parentheses, just to see if I could find the place where > it was breaking) will I have to worry about the ID clash, or is it > only a concern if you try to add a second instance of an ID to the DOM? > > Thanks again for all your help. > > Walter > > On Apr 19, 2008, at 6:32 PM, kangax wrote: > > > > > Sorry, > > that should have been: > > > ... > > if ($F(elm) != 'Other...') return; > > ... > > > - kangax --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
