Add failing test for forwarding element modifiers (execution order not affected by splattributes' location)

[cibernox]

trafficstars

Now that element modifiers are forwarded with the splattibutes, I was expecting to be able to decide in my components if my event handlers run before or after those provided by the users.

Example:

{{!-- my-component.hbs --}}
<div {{on "click" this.defaultHandler}} ...attributes>hello</div>

<MyComponent {{on "click" this.userProvidedHandler}} />

In this scenario I'd expect this.defaultHandler to always be called first, because the user-provided handler is applied with the ...attributes AFTER.

In this other scenario however:

{{!-- my-component.hbs --}}
<div ...attributes {{on "click" this.defaultHandler}}>hello</div>

<MyComponent {{on "click" this.userProvidedHandler}} />

I was expecting this.userProvidedHandler to be called first, and then this.defaultHandler, because the ...attributes is placed before in the div element.

Being able to decide the order of events is important to be able to call event.stopImmediatePropagation() and reliably know what handlers will not run.

That doesn't seem to be the case. Right regardless of where the ...attributes is placed, the user-provided event is invoked first.

[cibernox]

@chancancode You may have insight on this, IIRC you helped with RFC 435

[rwjblue]

I personally think these failing tests should be made to pass, but the first thing I'd like to confirm (with @chancancode / @wycats / @krisselden) is that this is the intended behavior.

[kategengler]

Is this still relevant?