@Chrissels Thanks for your report, I'm going to fix this in v3.5.2.