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
Trying to commit an invalid input when autoOpenDisabled = true results in the value property holding the previous value, unlike autoOpenDisabled = false where the value property is cleared in that case.
vursen
changed the title
[date-picker] Committing an invalid input doesn't reset the component's value when autoOpenDisabled
[date-picker] The value property isn't reset when committing an invalid input and autoOpenDisabled
Nov 22, 2022
vursen
changed the title
[date-picker] The value property isn't reset when committing an invalid input and autoOpenDisabled
[date-picker] The value property is not reset when committing an invalid input and autoOpenDisabled
Nov 22, 2022
vursen
changed the title
[date-picker] The value property is not reset when committing an invalid input and autoOpenDisabled
[date-picker] The value property is not cleared when committing invalid input and autoOpenDisabled
Nov 25, 2022
Description
A finding from vaadin/flow-components#1158 (comment)
Trying to commit an invalid input when autoOpenDisabled = true results in the
value
property holding the previous value, unlike autoOpenDisabled = false where thevalue
property is cleared in that case.Screen.Recording.2022-11-22.at.17.13.22.mov
Related to vaadin/platform#3066
Expected outcome
The
value
property should be cleared when trying to commit an invalid input, the same way it currently works when autoOpenDisabled = falseMinimal reproducible example
Steps to reproduce
1/1/2022
and press Enter to commit the valuefoobar
and press EnterEnvironment
Vaadin version(s): Latest
OS: Mac OS
Browsers
Issue is not browser related
The text was updated successfully, but these errors were encountered: