The calciteInputInput
event is triggered early causing incorrect status
#9581
Labels
0 - new
New issues that need assignment.
bug
Bug reports for broken functionality. Issues should include a reproduction of the bug.
calcite-components
Issues specific to the @esri/calcite-components package.
impact - p2 - want for an upcoming milestone
User set priority impact status of p2 - want for an upcoming milestone
needs triage
Planning workflow - pending design/dev review.
Check existing issues
Actual Behavior
When a file is uploaded using the
calcite-input
component, thestatus
property does not change frominvalid
tovalid
as expected, even though the file upload is successful. This is because the event listener for thecalciteInputInput
event triggers before the file upload completes, causing the input status to remain invalid. Adding a timeout resolves the issue, indicating a timing problem with the event trigger.Expected Behavior
The timing of the even triggering should be adjusted so that the input
status
can correctly reflect the current state.Reproduction Sample
https://codepen.io/Dipali-Joshi/pen/ExzxYaX?editors=1000
Reproduction Steps
calcite-input
element at line10
is set to ‘invalid’ as a default.14
and23
to add a timeout to the code. Observe that this time the status changes successfully.Reproduction Version
2.8.0
Relevant Info
Logged as
BUG-000167336
Regression?
No response
Priority impact
impact - p2 - want for an upcoming milestone
Impact
No response
Calcite package
Esri team
N/A
The text was updated successfully, but these errors were encountered: