1
ValueChange Change History
2
==========================
12
* Changed the name of the synthetic event to "valuechange" (all lowercase) for
13
greater consistency with DOM event names. The older "valueChange" name will
14
continue to be supported indefinitely, but for consistency I recommend
15
switching to "valuechange".
17
* Added support for delegated valuechange events. You can now use `delegate()`
18
to attach a valuechange event to a container node and be notified of changes
19
to any descendant that matches the specified delegation filter.
21
* The valuechange event facade now includes `currentTarget` and `target`
22
properties like a good little synthetic event.
40
* Focus is now used (in addition to keyboard and mouse events) as a sign that
41
we should begin polling for value changes. [Ticket #2529294]
43
* If the value changes while an element is not focused, that change will no
44
longer be reported the next time polling is started (since it couldn't have
51
* Module renamed to `event-valuechange` and refactored to be a true synthetic
54
* The `value` and `oldValue` event facade properties were renamed to `newVal`
55
and `prevVal` respectively, for consistency with other change event facades
56
throughout the library.
58
* Performance improvements.
76
* Initial release as `value-change`.