Yes, this seems to be the issue, thanks.

I couldn’t find this issue on GitHub before I posted here. I just noticed this on my 2.4.0 install and tested on the latest 5.3.0 version where the issue wasn’t there. I did try to explicitly limit the issue to 2.4.0 which others also might still use and didn’t want to make it look like 5.3.0 is the only version where it is fixed.