Logged In: YES
user_id=97919

Hi Jirka,

Thanks for noticing and documenting this behaviour. We
have been able to reproduce this in-house. This issue has
been assigned the tracking number S9E12-002513. This will
be fixed in a future release.

Thanks,
Narayanan.