This issue is confirmed to exist in the testing weekly build generated
on Sep. 2nd 2019.

Reply via email to