I just saw that there is already a version 3.5.3 which seems to have fixed this bug (I was testing with 3.5.1)
Sorry for the noise
Sorry for the noise