Hi VictorC,
Thanks for report! I was able to reproduce this behavior in 4.7.6, however it is not happening in our main internal build. fix should be included in next release, 4.8, and any Preview builds for 4.8 that we may do. Please let us know if you continue to see this occur after 4.8 is release. Thanks!