@sezare56, @avantronica I dug this out of a bug report I made from dec 2014:
So the issue has been around, I did not get a direct response about it from support because it was secondary to the main issue I wrote about and I did not give them steps to reproduce…