Sorry for the inconvenience.
We have not included the fix for the reported issue in our last weekly release, as we need to confirm the fix with all possible functionalities in the component. As promised in our previous update, we will include the fix in our January second weekly release which is expected to be rolled out by next week.
We appreciate your patience till then.
Shameer Ali Baig S.