Comment 4 for bug 1823367

Thanks, Dan!

I started using (onVerb) because I was concerned (verb) might conflict with built-in events. Apparently, this can have some unexpected consequences.

https://stackoverflow.com/questions/40276400/what-are-recommanditions-for-output-event-names-to-prevent-native-event-name-c

https://medium.com/angular-athens/naming-of-output-events-in-angular-2063cad94183

We do have some that would collide if the "on" was removed, so I'm hesitant to do a global search/replace. One suggestion I saw was to prefix the @Output name with something that describes the action.

E.g. Instead of:

<eg-org-select (onChange)=.../>

You might have:

<eg-org-select (orgChange)=.../>