equal
deleted
inserted
replaced
|
1 ValueChange Change History |
|
2 ========================== |
|
3 |
|
4 3.10.3 |
|
5 ------ |
|
6 |
|
7 * No changes. |
|
8 |
|
9 3.10.2 |
|
10 ------ |
|
11 |
|
12 * No changes. |
|
13 |
|
14 3.10.1 |
|
15 ------ |
|
16 |
|
17 * No changes. |
|
18 |
|
19 3.10.0 |
|
20 ------ |
|
21 |
|
22 * No changes. |
|
23 |
|
24 3.9.1 |
|
25 ----- |
|
26 |
|
27 * No changes. |
|
28 |
|
29 3.9.0 |
|
30 ----- |
|
31 * No changes. |
|
32 |
|
33 3.8.1 |
|
34 ----- |
|
35 |
|
36 * No changes. |
|
37 |
|
38 3.8.0 |
|
39 ----- |
|
40 |
|
41 * No changes. |
|
42 |
|
43 3.7.3 |
|
44 ----- |
|
45 |
|
46 * No changes. |
|
47 |
|
48 3.7.2 |
|
49 ----- |
|
50 |
|
51 * No changes. |
|
52 |
|
53 3.7.1 |
|
54 ----- |
|
55 |
|
56 * No changes. |
|
57 |
|
58 3.7.0 |
|
59 ----- |
|
60 |
|
61 * No changes. |
|
62 |
|
63 3.6.0 |
|
64 ----- |
|
65 |
|
66 * No changes. |
|
67 |
|
68 3.5.1 |
|
69 ----- |
|
70 |
|
71 * No changes. |
|
72 |
|
73 3.5.0 |
|
74 ----- |
|
75 |
|
76 * Changed the name of the synthetic event to "valuechange" (all lowercase) for |
|
77 greater consistency with DOM event names. The older "valueChange" name will |
|
78 continue to be supported indefinitely, but for consistency I recommend |
|
79 switching to "valuechange". |
|
80 |
|
81 * Added support for delegated valuechange events. You can now use `delegate()` |
|
82 to attach a valuechange event to a container node and be notified of changes |
|
83 to any descendant that matches the specified delegation filter. |
|
84 |
|
85 * The valuechange event facade now includes `currentTarget` and `target` |
|
86 properties like a good little synthetic event. |
|
87 |
|
88 |
|
89 3.4.1 |
|
90 ----- |
|
91 |
|
92 * No changes. |
|
93 |
|
94 |
|
95 3.4.0 |
|
96 ----- |
|
97 |
|
98 * No changes. |
|
99 |
|
100 |
|
101 3.3.0 |
|
102 ----- |
|
103 |
|
104 * Focus is now used (in addition to keyboard and mouse events) as a sign that |
|
105 we should begin polling for value changes. [Ticket #2529294] |
|
106 |
|
107 * If the value changes while an element is not focused, that change will no |
|
108 longer be reported the next time polling is started (since it couldn't have |
|
109 been user input). |
|
110 |
|
111 |
|
112 3.2.0 |
|
113 ----- |
|
114 |
|
115 * Module renamed to `event-valuechange` and refactored to be a true synthetic |
|
116 event. |
|
117 |
|
118 * The `value` and `oldValue` event facade properties were renamed to `newVal` |
|
119 and `prevVal` respectively, for consistency with other change event facades |
|
120 throughout the library. |
|
121 |
|
122 * Performance improvements. |
|
123 |
|
124 |
|
125 3.1.2 |
|
126 ----- |
|
127 |
|
128 * No changes. |
|
129 |
|
130 |
|
131 3.1.1 |
|
132 ----- |
|
133 |
|
134 * No changes. |
|
135 |
|
136 |
|
137 3.1.0 |
|
138 ----- |
|
139 |
|
140 * Initial release as `value-change`. |