It was kind of a stretch for it being an instance issue anyway, but thanks for the response. (These issues started after the last instance update, which does point the finger at the client in many cases. Not all, but many.)

Unfortunately, my manipulation skills are top tier. Unless you happen to have the memory span of a carrot, this issue report is now planted in your head as something to associate with any possible future issues that you might encounter. (I know how engineers think, bud.)

Ok, maybe I just have a little too much time on my hands at the moment to type out extended comments. ;)