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
Seems a bug in 1.26.0 for Date picker that was not there in 1.21.0. Visit: https://web-components.carbondesignsystem.com/?path=/story/components-date-picker--single-with-calendar and open and select a date. It will work as expected and fire the event. Open it again and try to select another date. It fires the event, but does NOT actually select the value. Then click again and it WILL select date and fire yet again.
Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.
Description
Seems a bug in 1.26.0 for Date picker that was not there in 1.21.0. Visit: https://web-components.carbondesignsystem.com/?path=/story/components-date-picker--single-with-calendar and open and select a date. It will work as expected and fire the event. Open it again and try to select another date. It fires the event, but does NOT actually select the value. Then click again and it WILL select date and fire yet again.
Component(s) impacted
bx-date-picker. Use the 1.26.0 story to verify issue as described above: https://web-components.carbondesignsystem.com/?path=/story/components-date-picker--single-with-calendar
Browser
Chrome, Firefox
Carbon for IBM.com version
v1.26.0
Severity
Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.
Application/website
IBM Customer Connect (https://www.ibm.com/technologyconnect)
Package
@carbon/ibmdotcom-web-components, @carbon/web-components
CodeSandbox example
https://web-components.carbondesignsystem.com/?path=/story/components-date-picker--single-with-calendar
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: