component events should mask event propagation.

@Component({
  selector: 'my-component'
  events: ['change']
})
@View({
  template: '<input (change)="...">'
})
class MyComponent {
} 

The above code creates an issue. It conflates the change event from the MyComponent with the bubbling change event from the <input>.

The correct behavior is that the change event which is part of the components should filter out the DOM change events. Otherwise

<my-component (change)="doSomething($event)">

will sometimes get the $event from the MyComponent and sometimes from the input event.

[Giwayume]

I have to say, Angular 2 is the most stressful Javascript framework I’ve had to deal with (due to its adoption at work). It is somehow paradoxically both over-engineered and not well thought out.

[mhevery]

I have to say, Angular 2 is the most stressful Javascript framework I’ve had to deal with (due to its adoption at work). It is somehow paradoxically both over-engineered and not well thought out.

@Giwayume I understand that you are frustrated, and I also understand that things are not perfect, but such comments are not constructive and do not create value. Please stay on subject here.