I’m fairly certain that this issue has already been fixed, but from what i can tell it has not been released yet. We’re about to release 6.2.6, and it should be included in that one.

I will still add a test for the issue, thanks fro reporting it!