You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.
It does this at the polymer-expressions layer. I think this is very common behavior and should be a concern of element's NodeBind.
Here's how I propose this work:
HTMLElement allows binding to 'on-', by setting up a binding to the event whose name is the first N non-whitespace characters following 'on-'. The behavior of the binding is to
One thing to note here is that the bindingValue doesn't really need to be an observer, even though it is dynamic. It's sufficient to retrieve the value when the event is handled.
Thus the implementation of the element that handles the binding might not call open(), but only getValue() on the observable.
The text was updated successfully, but these errors were encountered:
Polymer supports this following kind of thing:
It does this at the polymer-expressions layer. I think this is very common behavior and should be a concern of element's NodeBind.
Here's how I propose this work:
HTMLElement allows binding to 'on-', by setting up a binding to the event whose name is the first N non-whitespace characters following 'on-'. The behavior of the binding is to
One thing to note here is that the bindingValue doesn't really need to be an observer, even though it is dynamic. It's sufficient to retrieve the value when the event is handled.
Thus the implementation of the element that handles the binding might not call open(), but only getValue() on the observable.
The text was updated successfully, but these errors were encountered: