Depends on what version of Tapestry you are using.
Explicit ordering of mixins is in trunk.
Robert
On Mar 17, 2010, at 3/178:50 AM , Michael Prescott wrote:
As I understand it, mixin order is unspecified. A developer on our
team had
this issue and wound up implementing a custom component, IIRC.
Michael
On Wed, Mar 17, 2010 at 11:45 AM, LiborGMC <l.pre...@gmc.net> wrote:
Hi there,
I've implemented two mixins which just add some JavaScript code to
action
onClick to actionLink. I defined these two mixins to one
actionLink. I
expect that order in which mixins are fired is the same as I
defined in
"t:mixins" attribute. Firefox 3 is keeping this order but IE 8
isn't. Can I
specify somehow the order of processing of mixins?
I think it is bug I would expected that behaviour is independent
from type
of browser.
Regards
--
View this message in context:
http://old.nabble.com/Order-of-processing-of-mixins-tp27933566p27933566.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
