[ 
http://issues.apache.org/jira/browse/TAPESTRY-1209?page=comments#action_12460446
 ] 
            
Grzegorz Mrowka commented on TAPESTRY-1209:
-------------------------------------------

sorry for creating confusion. I was thinking (and still I do) that it is 
generally Dojo vs Tapestry related issue rather then tacos4.1 and Andreas'es 
DojoWidget component. I used tacos only as an example. First I had ajax refresh 
problem with my own implementation of dojo ContentPane.
I think that the same problem will apply to tapestry TitlePane component as 
well.
Merry Christmas and Happy New Year!

> Ajax refresh (updateComponents) on components located in dojo Widget
> --------------------------------------------------------------------
>
>                 Key: TAPESTRY-1209
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1209
>             Project: Tapestry
>          Issue Type: Bug
>          Components: XHR/dhtml/Ajax
>    Affects Versions: 4.1.2
>         Environment: Firefox 1.5.0.9
>            Reporter: Grzegorz Mrowka
>         Attachments: Test.html, Test.java
>
>
> Ajax refresh (updateComponents parameter) on components located in dojo 
> Widget (ContentPane, TabContainer, ...) not working. 
> Changes are visible only after page reloading or only when updateComponents 
> contains parent widget's id.
> To show this I have used tacos 4.1 and DojoWidget, but this is not the 
> DojoWidget problem.
> Problem is that DOM element which I want to refresh in ajax way is a child of 
> some widget.
> The problem is increasing when ContentPane is a child of TabContainer. 
> Sample code was attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to