You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2007/06/15 16:20:25 UTC

[jira] Created: (TAPESTRY-1580) AJAX response to update a component doesn't include the updated component's root tag

AJAX response to update a component doesn't include the updated component's root tag
------------------------------------------------------------------------------------

                 Key: TAPESTRY-1580
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1580
             Project: Tapestry
          Issue Type: Bug
          Components: Framework
    Affects Versions: 4.1.2
            Reporter: Marcus Schulte
            Priority: Minor
             Fix For: 4.1.2


Currently a component scheduled to be updated in an ajax request via @EventListener gets only its body replaced. 
This leads to somewhat counterintuitive behaviour. 
E.g.: Firefox accepts the xml-snippets with multiple root elements, that can result from this, IE 6 does not.

Since it's easy to work around that, it could also fixed by documenting it if it's hard to do otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Updated: (TAPESTRY-1580) AJAX response to update a component doesn't include the updated component's root tag

Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesse Kuhnert updated TAPESTRY-1580:
------------------------------------

    Fix Version/s:     (was: 4.1.2)
                   4.1.3

> AJAX response to update a component doesn't include the updated component's root tag
> ------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1580
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1580
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.1.2
>            Reporter: Marcus Schulte
>            Priority: Minor
>             Fix For: 4.1.3
>
>
> Currently a component scheduled to be updated in an ajax request via @EventListener gets only its body replaced. 
> This leads to somewhat counterintuitive behaviour. 
> E.g.: Firefox accepts the xml-snippets with multiple root elements, that can result from this, IE 6 does not.
> Since it's easy to work around that, it could also fixed by documenting it if it's hard to do otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Closed: (TAPESTRY-1580) AJAX response to update a component doesn't include the updated component's root tag

Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Schulte closed TAPESTRY-1580.
------------------------------------

    Resolution: Invalid

Is fixed in 4.1.2. Somehow, I must have worked with a wrong jar.

> AJAX response to update a component doesn't include the updated component's root tag
> ------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1580
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1580
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.1.2
>            Reporter: Marcus Schulte
>            Priority: Minor
>             Fix For: 4.1.3
>
>
> Currently a component scheduled to be updated in an ajax request via @EventListener gets only its body replaced. 
> This leads to somewhat counterintuitive behaviour. 
> E.g.: Firefox accepts the xml-snippets with multiple root elements, that can result from this, IE 6 does not.
> Since it's easy to work around that, it could also fixed by documenting it if it's hard to do otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Commented: (TAPESTRY-1580) AJAX response to update a component doesn't include the updated component's root tag

Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507664 ] 

Marcus Schulte commented on TAPESTRY-1580:
------------------------------------------

Wouldn't dare to change this now. A clear statement in the responsebuilder docs should be sufficient to prevent anybody from falling into the same trap.

> AJAX response to update a component doesn't include the updated component's root tag
> ------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1580
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1580
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.1.2
>            Reporter: Marcus Schulte
>            Priority: Minor
>             Fix For: 4.1.2
>
>
> Currently a component scheduled to be updated in an ajax request via @EventListener gets only its body replaced. 
> This leads to somewhat counterintuitive behaviour. 
> E.g.: Firefox accepts the xml-snippets with multiple root elements, that can result from this, IE 6 does not.
> Since it's easy to work around that, it could also fixed by documenting it if it's hard to do otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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