I'd recommend not using IDs at all for simplicity. Instead, use the DOM traversal methods:
var highlight = function(originalRequest){
	new Effect.Highlight($(id).down());
}

Colin

Graham wrote:
Aahh. I see. Well I'll take a look at that tomorrow and work out some
kind of loop to increment the dive number.
Thanks for your help Dave.
Graham

On Mar 1, 4:19 pm, dave crane <[EMAIL PROTECTED]> wrote:
  
Hi Graham,

Just had a quick look at this in Firebug. It looks like all your DIV tags are
coming back with an ID of 'test'. so the Effect is just going to go for the first
one with that name. Looks like a race condition is underway here - although the
updateContent() gets called before onComplete(), the first time the Effect is
invoked, the content hasn't been rendered yet, so it selects the previous one.

If you increment the id of the div each time (test_1, test_2) etc., you'll avoid
this kind of confusion - or you could pass the id of the incoming DIV to be
highlighted as an X-JSON header, maybe?

HTH

Dave
    




  

--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to