Gar

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

+1 this probably needs to be done at least to match class bindings, i.e. style, booleanStyle, switchStyle

`onlyOnce` makes sense as a name to me, and I wonder if `once` with multiple names should log a warning. I for one would have fallen into the same assumption....

What would be the benefit of this, outside a feeling of familiarity for someone used to `EventEmitter`? I'm on the fence about this personally. Adding aliases is relatively easy to...

Just a suggestion to keep the nomenclature matching the other 'class' methods (i.e. amp-add-class) which would make this `amp-extend-class` I'm a little lukewarm about renaming amp-extend since it's an already...

This lib is pretty heavily coupled to the html form DOM. So whatever would cause a submit event to fire from `this.el` will trigger the 'submit' process in this library....

Ah yes I see now what you mean. The `fieldContainer` needs to be added to the readme. You can build a form with a submit button in it in your...

I believe you could also use an input-view with type `submit` but I haven't seen that personally.

Check out this tweak on the readme example: http://esnextb.in/?gist=9d1127976d78d3e17eb4

I seem to remember there was some sort of bug we fixed that allowed form inputs to validate based on the states of other inputs in the same form, as...