Confused by mixins render order. Bug?

[Barry Books]

I created a test page with some test mixins. The page contains

<t:any t:mixins="M1,M2">stuff</t:any>

    <t:form>
    <t:select t:mixins="M1,M2" model="literal:a,b,c" value="test"/>
    </t:form>

The M1,M2 mixins do something like this

        void beginRender() {
                logger.info("begin m1");
        }
        
        void afterRender() {
                logger.info("after m1");
        }

I also have a mixin called selector which is added like this


model.addMixinClassName(Selector.class.getName(),"before:*");           

My logger output is this

[INFO] mixins.Selector push element Test:any$selector
[INFO] mixins.M1 begin m1
[INFO] mixins.M2 begin m2
[INFO] mixins.M2 after m2
[INFO] mixins.M1 after m1
[INFO] mixins.Selector pop element Test:any$selector
[INFO] mixins.Selector push element Test:form$selector
[INFO] mixins.M1 begin m1
[INFO] mixins.M2 begin m2
[INFO] mixins.Selector push element Test:select$selector
[INFO] mixins.Selector pop element Test:select$selector
[INFO] mixins.M2 after m2
[INFO] mixins.M1 after m1
[INFO] mixins.Selector pop element Test:form$selector


The any component behaves like I would expect. The selector mixins
beginRender is first and it's afterRender is last. However the select
component render order
seems broken to me. Why does the selector mixin for the select
component render after the m1 and m2 mixins?

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