I believe this has been fixed in the most recent version - at least, I can't reproduce it in the bleeding edge build.
