2 comments

Frank J The bug has been reproduced and assigned to the responsible developer. Unfortunately, due to time and resources, it was not fixed yet.

0

Is there an ETA?

0

Please sign in to leave a comment.