On Jan 27, 2008 9:46 PM, Gareth Evans <[EMAIL PROTECTED]> wrote: > Thanks for getting back to me, > I found that the startTagAdd function was causing execution to stop without > a javascript error, which meant the e.stop() never got called.
Yes, that would cause the error :) I just typically do "return false" on my form submit handlers, just to make sure, but you are right, you shouldn't need it. Nathan, I've never used event.preventDefault() but it looks like that would work too. Event.stop(event) was the pre-1.6.0 Prototype way to stop events from bubbling up, but now we can just do event.stop(). -justin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
