Depends on how you are doing it. If you are using the elements .innerHTML to get the data out again, you are fine. If you are using the DOM functionality (.childNodes,.createElement,etc) you will need to take in account for the update lag in IE.
However, I have not heard of this onReady() functionality before. I will have to look into it as it sounds like an amazingly helpful idea for IE. ********************************* Andrew Martinez ([EMAIL PROTECTED]) ********************************* > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:rails-spinoffs- > [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Saturday, July 01, 2006 3:03 PM > To: [email protected] > Subject: RE: [Rails-spinoffs] iframe ... does it have an innerHTML ? > > > > And here is the kicker: > > - In IE only: if you use innerHTML there is a 1ms-100ms lag > > between > > the DOM tree/DOM nodes being updated with your new HTML. However it is > > instantly visible to the user. > > > > > > I have been using innerHTML to insert Ajax retrieved content and > applying > > observers to that content using EventSelectors without any problem. > > > > But I'd like to be safe. Is there a safer way to know when the DOM tree > > is > > ready before applying observers ? > > You could use DOM.Ready, specifically the onIdReady() function. > > http://openjsan.org/doc/a/au/autarch/DOM/Ready/0.13/lib/DOM/Ready.html > _______________________________________________ > Rails-spinoffs mailing list > [email protected] > http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs _______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
