tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikk Folts (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-260) Autocompleter mixin doesn't work when inside zone and after update
Date Mon, 09 Apr 2012 21:25:16 GMT

    [ https://issues.apache.org/jira/browse/TAP5-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250197#comment-13250197
] 

Nikk Folts commented on TAP5-260:
---------------------------------

Same thing is happening for me, and that JS error causes other parts of the page to not work.
                
> Autocompleter mixin doesn't work when inside zone and after update
> ------------------------------------------------------------------
>
>                 Key: TAP5-260
>                 URL: https://issues.apache.org/jira/browse/TAP5-260
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.15
>            Reporter: Hugo Palma
>            Assignee: Howard M. Lewis Ship
>
> I have a textfield with the autocompleter mixin inside a zone. Everything works fine
until some event updates the zone.
> After that first update i start getting the following javascript error.
> After some digging i found that what is happening is that when the autcompleter mixin
renders again as the zone is updated it generates a new id for it. This id is used to register
with the Ajax.Autocompleter javascript object. The problem is that the previous render had
already registered the same Ajax.Autocompleter object listener but for the previous id that
doesn't id anymore, hence the error.
> $(element) is null			prototype.js (line 1577)
> hide()("subject:11ce7b19c7a:loader")
> stopIndicator()()   controls.js (line 126)
> hide()()controls.js (line 116)
> (?)()()prototype.js (line 209)    
> $(element).style.display = 'none';prototype.js (line 1577

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message