Comment 5 for bug 1823367

I wondered if something like that might be the reason. Bummer.

Oddly enough, they use a lot of examples like (verb), and as a commenter pointed out, they specifically say to not use onVerb for output properties in the Angular style guide:

https://angular.io/guide/styleguide#dont-prefix-output-properties

Also from one of your links, the second half of the following statement, if accurate, worries me:

"We should not use output and input names that collide with either a native property/event name or even an input/output name used by any other component or directive."

Maybe I'm naive, but that seems to put a giant damper and the whole component reusability angle, I would think.

I'm going to need to play around with it a little more to actually get a feel for different approaches. Maybe the tried and true eg- prefix (egClick, egChange, etc.) could be another option.

P.S. I reviewed and pushed the first chunk of this branch (#1818288) to master and rel_3_3, and will continue with the next chunk. Thanks, Bill!