You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the input is focused, you can enter the date via the keyboard, such as "01", "01", "1980". As soon as you type the "1" for the year fecha throws an error because the Date field currently has "01/01/0001" but Chrome allows you to continue appending to the value by entering the other 3 digits. fecha throws 3 errors during this time, as "0001", "0019" and "0198" are invalid years but the user has not finished entering the date.
The same error occurs when you use the "x" in Chrome to clear the field. When clearing the field value, the value is not "null" and appears to be an empty string. fieldInput checks against null.
Once the date has been made valid, the model is not properly updated to reflect the correct value. Once the fecha errors are thrown, data binding appears to break ... clearing the field with the "x" and using the built-in date dropdown prevents the model from being updated as well.
The text was updated successfully, but these errors were encountered:
* master:
reverting back to original test
reverted back to `schema.required` for "none selected" disabled state, per @icebobfixesvue-generators#340 - "none" value set to `null`, formatValueToField checks for `isNil(value)` and returns `null`, none options are always disabled
fixesvue-generators#362 - `integer` validator now calls `number` validator, and returns `invalidIntegerl: "The value is not an integer"` as well as any errors generated by `number`
fixesvue-generators#361 - use $event.target.valueAsNumber for number/range inputs, debounce `formatValueToModel` for number/range, removed `formatValueToField`
added missing comma that failed in Travis
requested by @icebobfixesvue-generators#341 - introduced debounce functionality into `formatValueToModel`
# Conflicts:
# dist/vfg-core.js
# dist/vfg.js
# package-lock.json
When entering dates manually using the keyboard in Chrome, fecha throws errors.
JSFiddle: https://jsfiddle.net/zoul0813/21ba3on5/
When the input is focused, you can enter the date via the keyboard, such as "01", "01", "1980". As soon as you type the "1" for the year fecha throws an error because the Date field currently has "01/01/0001" but Chrome allows you to continue appending to the value by entering the other 3 digits. fecha throws 3 errors during this time, as "0001", "0019" and "0198" are invalid years but the user has not finished entering the date.
The same error occurs when you use the "x" in Chrome to clear the field. When clearing the field value, the value is not "null" and appears to be an empty string. fieldInput checks against null.
Once the date has been made valid, the model is not properly updated to reflect the correct value. Once the fecha errors are thrown, data binding appears to break ... clearing the field with the "x" and using the built-in date dropdown prevents the model from being updated as well.
The text was updated successfully, but these errors were encountered: