Howdy Douglas,
I am sorry to make you open a new topic. I believe that was accidentally closed.
I just checked through our logs, and it seems two QA folks saw the issue go away in Safari, but one still saw it crop up during on of her tests. The remaining one who saw it concluded that they were doing something wrong, like perhaps not having cleared their browser cache, and said it was a pass. Since you are still seeing this issue I am going to query them. It might be that the outlier QA person is able to replicate your problem and can help us get to the bottom of it. I am leaving a question for them, to answer tomorrow, then we will get back to you. Thanks for following up Douglas.