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
I don't know if that has been discussed already, but when using the DateRangePicker and Bootstrap 5, the second input does nto have rounded corners.
This seems to be an issue with the css-selector "not last child", because the datepicker is added as a div after the input. It also shows in the live example.
Is there a workaround for that?
The text was updated successfully, but these errors were encountered:
Thank you for reporting this. I should have been more careful when checking the demo.
You are right. It's caused by this library's inserting picker div element after the input element, which makes the input element no longer the last item of input-group. I guess the reason why this has never been discussed is that people usually have a validation message div after the input and don't encounter this problem.
The least hacky workaround is probably adding a wrapper div around the input-group and attach date range picker to the wrapper with setting the wrapper to the container option.
Right, the validation message is not necessary in my case. You solution looks good, however I solved it by changing the css query that is used by Bootstrap, since I'm using scss anyways. Somethin in the lines of
form-control:last-of-element {
/* set rounded corners */border-radius: 0,$input-border-radius,$input-border-radius,0;
}
I don't remember how exactly I did it, but that worked for me at least 😄 I didn't see the possibility of assinging a container element.
Hi there,
I don't know if that has been discussed already, but when using the DateRangePicker and Bootstrap 5, the second input does nto have rounded corners.
This seems to be an issue with the css-selector "not last child", because the datepicker is added as a div after the input. It also shows in the live example.
Is there a workaround for that?
The text was updated successfully, but these errors were encountered: