EventBehaviors rendered in reverse order

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Instantiate and add an container
     WebMarkupContainer container = new WebMarkupContainer("container");
     add(container);
2.Add some behaviors with the same event (e.g. "onclick")
     container.add(new WiQueryEventBehavior(new Event(MouseEvent.CLICK){

          @Override
          public JsScope callback(){
               return JsScope.quickScope("console.log('one')");
          }
          }));
     container.add(new WiQueryEventBehavior(new Event(MouseEvent.CLICK){

          @Override
          public JsScope callback(){
               return JsScope.quickScope("console.log('two')");
          }
          }));
     container.add(new WiQueryEventBehavior(new Event(MouseEvent.CLICK){

          @Override
          public JsScope callback(){
               return JsScope.quickScope("console.log('three')");
          }
          }));

What is the expected output? What do you see instead?
Expected result:
"one"
"two"
"three"
What I get:
"three"
"two"
"one"

What version of the product are you using? On what operating system?
wiquery 1.5.5
with 
Wicket 1.5.5

Providing a good description and a patch or a quickstart [1] will really
help us fixing the problem quickly! Please provide any additional
information below.
AjaxEventBehavior is also affected.
In 1.2.4 the order of the rendered Statements are correct.

[1] http://code.google.com/p/wiquery/wiki/Quickstart15

Original issue reported on code.google.com by thomas.f...@googlemail.com on 27 Jun 2012 at 1:49

[GoogleCodeExporter]

I just noticed this - v1.5.7 - actually breaks some functionality when the JS 
is rendered in the wrong/unexpected order.

Original comment by nbpr...@gmail.com on 16 Aug 2012 at 7:43

[GoogleCodeExporter]

The issue was either
-not reproducable
-there is a newer version available
-reported in a version which is no longer supported

if the issue is still present in the latest version (6.9+) then please reopen 
the issue with the required information to reproduce the issue.

Original comment by hielke.hoeve on 26 Nov 2013 at 8:37

• Changed state: Fixed