You are right. I filed a bug internally.

Firmware 4.x does not have this problem.

1 Like