Hey Nitecon,
I apologize for delay in response. This is in fact a bug, and it appears to no longer be an issue in our internal build. I know that it is fixed for 4.4, and I am checking now to see if it is fixed in 4.3 which should be available very soon. I will let you know once I have confirmed. Thanks for your report!