#28737

We’ve just fixed the issue in the development build. The fix will be available with the next maintenance release.