coreui / coreui-pro / 39068880831

96%

main: 94%

push

github

fix: report a form control's value change only when the user or the component makes it (#1684)

Form controls now report a value change only when the user or the component makes it, a native form reset included, and never for a value the page gives.

MultiSelect fires `change` (with the native `input` and `change`) when a form reset restores the start selection, and stays silent when `setOptions()` brings the options a given `value` names or when `setConfig()` sets the selection. OTP Input, Combobox `setValue()`/`clear()`, Rating `reset()`, Autocomplete `clear()` and Range's `changed` fire only when the value changes. OTP Input and Range Slider now fire on a form reset that changes the value, and Date Input sends the native events of its value field there. A form reset brings Rating and Range Slider back to the value they were built with rather than one a later `setConfig()` gave (a handle `setConfig()` adds starts at the value it was added with), and OTP Input's `reset()` puts back the code it started with, as the native reset does. A read-only Rating keeps its restored star the one tab stop, and the stepper keeps its validation marks when a listener cancels the reset.

Rating's `reset(value)` keeps its documented meaning (clear, or set the given value) and only stops firing without a change. Date Input and Time Input keep firing from `setConfig({ date })`, their only way to set the value from code, which the docs now say.

7701 of 8256 branches covered (93.28%)

Branch coverage included in aggregate %.

60 of 61 new or added lines in 9 files covered. (98.36%)

13262 of 13551 relevant lines covered (97.87%)

1970.03 hits per line