You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Magnus Rundberget <ru...@me.com> on 2009/07/24 13:09:29 UTC

autocomplete mixin within zone problem

Hi,

I´m experiencing javascript errors when using the autocomplete mixin  
in a zone.
(found the following closed issue that I added a comment to : https://issues.apache.org/jira/browse/TAP5-260 
  )

Seems there is a problem (at least for me) when using autocomplete  
inside a zone, doing something (other than submitting form with  
autocomplete field) that refreshes the zone and the autocomplete field  
has focus. A javascript error (element is null) is generated.

Anyone else experiencing the same problem ? Any suggestions for a  
workaround ?

cheers
magnus

RE: autocomplete mixin within zone problem

Posted by De Saint Steban Emmanuel <em...@atosorigin.com>.
I have exactly the same problem with form fragment. It is because the javascript which init the component (autocomplete, forma fragment, form validation and other ...) was relaoeded with the zone. You can see the javascript fonction on the bottom of the page. But when the zone was reloeded, this finction was not call. I didn't know how to reload this fonction.

If anyone have an idee about this issue, I am interested. I have posted a question about it with no answer.

Emmanuek

-----Message d'origine-----
De : Magnus Rundberget [mailto:rundis@me.com]
Envoyé : vendredi 24 juillet 2009 13:09
À : Tapestry users
Objet : autocomplete mixin within zone problem

Hi,

I´m experiencing javascript errors when using the autocomplete mixin
in a zone.
(found the following closed issue that I added a comment to : https://issues.apache.org/jira/browse/TAP5-260
  )

Seems there is a problem (at least for me) when using autocomplete
inside a zone, doing something (other than submitting form with
autocomplete field) that refreshes the zone and the autocomplete field
has focus. A javascript error (element is null) is generated.

Anyone else experiencing the same problem ? Any suggestions for a
workaround ?

cheers
magnus


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org