Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
This is, unfortunately, still present in 4.7.3 so I logged another bug for it. Thanks though!