event-valuechange module adds a "valuechange" event that fires
value property of an
[contenteditable="true"] element changes as the result of a keystroke,
mouse operation, or input method editor (IME) input event.
The input related events provided by browsers don't cleanly address the
variety of ways users can modify an
value. For example, users might change an input value by:
The ideal change event would fire when the value becomes something it wasn't a moment ago.
valuechange event provides more reliable input notifications than
native events like
textInput, particularly with changes that
result from multiple-keystroke IME input.
valuechange subscriptions monitor the element's value using a variety of
mechanisms including subscriptions to
focus and various keyboard events, and a
poll to catch the stragglers. It seems like a lot of work, but it's the only
way to be sure.
Polling is only active when the element is focused, and only one element is polled at a time, so the performance of your app should not be impacted.
valuechange only supports subscriptions on
[contenteditable="true"] elements, although it
doesn't prevent you from subscribing on other types of elements.
If you subscribe on a different type of element and stuff breaks,
you were warned.
valuechange does not capture
unless the input is currently focused and polling. It's meant
to capture changes made by the user, not by other code. So:
node.set('value', 'probably will not trigger valuechange');