If you're replacing the element you're observing, that's your problem
-- events are observed on instances. Even if you replace an element
with the ID "X" with another element with the ID "X", they're
>From your description, it sounds like you're replacing more than you
really should be, but it's hard to tell without code. If it's not that
you're replacing the element you're observing, I'd suggest replicating
the problem in a small, self-contained example.
Independent Software Consultant
tj / crowder software / com
On Dec 13, 5:27 pm, Rui Campos <ruirccam...@gmail.com> wrote:
> I'm currently doing a college project on ruby on rails and I have to
> do a common Tag system for wiki pages. I have an observer "observing"
> a input field to check if a tag that the user is trying to add already
> has a similar one on the system, if there is one, a text box appears
> asking if the user wants to replace the tag introduced by the already
> in the system. The tag adding is made with ajax.
> The problem is that after the user adds a tag, meaning he clicks the
> add button and the ajax call refreshes the tag box, the observer stops
> working and i have to refresh the page. I'm not sure if this is a bug
> with my code or if it is intended. If it is intended, is there a work
> If there is already a discussion about a similar issue, I was unable
> to find it. Please direct me to it if possible : )
> Rui Campos.
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at