Currently, on:input event handlers are applied before any event handlers from actions or bindings, regardless of the order in which they're declared. This makes certain tasks (such as input masking) overly difficult.
Demos (which behave differently between Chrome and Firefox):
A solution would be to consistently apply directives in the order in which they're declared. It'll require some rejiggering though.
Currently,
on:inputevent handlers are applied before any event handlers from actions or bindings, regardless of the order in which they're declared. This makes certain tasks (such as input masking) overly difficult.Demos (which behave differently between Chrome and Firefox):
A solution would be to consistently apply directives in the order in which they're declared. It'll require some rejiggering though.