You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Josh Canfield (JIRA)" <ji...@apache.org> on 2011/08/22 06:48:29 UTC

[jira] [Resolved] (TAP5-1613) Mixin inherited from parent model does not inherit order

     [ https://issues.apache.org/jira/browse/TAP5-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Canfield resolved TAP5-1613.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3

First check the model to see if it defines ordering and return that if defined. 
If there is no order locally and there is a parent model, request ordering constraints from the parent.

> Mixin inherited from parent model does not inherit order
> --------------------------------------------------------
>
>                 Key: TAP5-1613
>                 URL: https://issues.apache.org/jira/browse/TAP5-1613
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2.5
>            Reporter: Josh Canfield
>            Assignee: Josh Canfield
>             Fix For: 5.3
>
>
> As reported on the user list: http://tapestry.1045711.n5.nabble.com/Confused-by-mixins-render-order-Bug-td4708340.html
> When a mixin is added to a parent component the mixin is inherited by the child component, but the ordering of the mixin is not.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira