This issue persists still, in version 4.16.3. Following your link, the issue has been placed on “backlog”. Any info on when a fix might be made would be greatly appreciated!
This issue persists still, in version 4.16.3. Following your link, the issue has been placed on “backlog”. Any info on when a fix might be made would be greatly appreciated!