Seeing a reply from one of the devs would be great. The other thread also didn’t have any replies. I am wondering why…
Are you not interested in fixing this? This is clearly a bug which can easily be reproduced. If you don’t want to fix this, then the documentation is invalid and needs to be changed, although it would be a breaking change in the v5 API scope.