It's not fixed. The recommended work-around is to not use the DatePicker with asynchronous loading. It was decided that QQC2/ UITK2, which has a DatePicker component, would make more sense to use in new code than rewriting what we have right now (you can see from the related branch starting some of this effort that it's basically a rewrite).
It's not fixed. The recommended work-around is to not use the DatePicker with asynchronous loading. It was decided that QQC2/ UITK2, which has a DatePicker component, would make more sense to use in new code than rewriting what we have right now (you can see from the related branch starting some of this effort that it's basically a rewrite).