Hi Michael, thanks for looking into this. When I went back to replicate the issue I found that software updates had been applied overnight, OS X is now at 10.11.5 (was 10.11.4), Safari is 9.1.1 (was 9.1) and the problem has gone away. I don’t think anyone will blame me for saying “I’m good with that” rather than rolling back to see if I can reproduce. 🙂
Thanks for a great product, don’t know how I ever got along without it.