Thanks for the reply @tygastrike, interesting to see this behaviour still happens on the latest version as well, although we have been unable to reproduce this issue in house. Accordingly, I will create the appropriate bug report for review at a future development meeting, although as I understand the problem, no functionality is impacted, never the less perhaps a simple fix can be integrated promptly. We appreciate your patience whilst we investigate the issue.