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
This bug is for the possibility to type a date by hand and not using the calendar widget.
For a range date picker, the onChange props is never called after typing in the second input (and not choosing a date in the calendar) and close the calendar.
It works for the first input. And of course it works normally by using the calendar widget for both input.
Suggested Severity
Severity 1 = Must be fixed ASAP. The response must be swift. Someone from the team must drop all current work and be immediately reassigned to address the issue.
@tay1orjones not closed by #13108 🥲, I think technically it would but there's a bug on top of this bug where the first date is getting deleted after doing step 1 and attempting step 2:
@tay1orjones@francinelucca I'm seeing this bug in the Flatpickr example here https://flatpickr.js.org/plugins/ is this something we can fix in Carbon, or is this an upstream bug? It seems that when you select the first date it expects you to select the second without clicking off of it. Perhaps not a bug, and just the way the component was intended to work?
I'd think it is a bug since the behavior seems very unexpected to me.
We could try and hack it if we wanted to, or wait for upstream to be fixed. Doesn't seem like there's much going on in the flatpickr repo tho' these days... Last published version is a year ago https://www.npmjs.com/package/flatpickr?activeTab=versions
Package
@carbon/react
Browser
Chrome
Package version
v1.11.0
React version
v17.0.2
Description
This bug is for the possibility to type a date by hand and not using the calendar widget.
For a range date picker, the onChange props is never called after typing in the second input (and not choosing a date in the calendar) and close the calendar.
It works for the first input. And of course it works normally by using the calendar widget for both input.
Suggested Severity
Severity 1 = Must be fixed ASAP. The response must be swift. Someone from the team must drop all current work and be immediately reassigned to address the issue.
Reproduction/example
https://stackblitz.com/edit/github-pzlus6-jt29yb?file=src/App.jsx
Steps to reproduce
Code of Conduct
The text was updated successfully, but these errors were encountered: