Hello,
You are correct, this has not been fixed for 4.3, 4.3.1 or 4.4 preview, however the report has just recently been updated as fixed and verified by our internal QA. The fix will go to the public binary in an upcoming release soon.
Thank you,
Hello,
You are correct, this has not been fixed for 4.3, 4.3.1 or 4.4 preview, however the report has just recently been updated as fixed and verified by our internal QA. The fix will go to the public binary in an upcoming release soon.
Thank you,