Hi,

I was unable to reproduce the mentioned behaviour
in both 1.0.154.53 and 1.0.154.48 versions of chrome
running on Windows XP SP3.

Can anyone else second or validate this ?

Reply via email to