Hello Guys,
I have checked this issue in 4.2 version which we are working on and I was unable to reproduce it.
Looks like the bug you reported is fixed in new version.

John