While I could reproduce this problem with 5.13.9, I cannot reproduce it with 5.13.10 nor with 5.13.11. So I think the issue has been resolved.