@Olivier Gagnon (DXC) Thanks for the info. Yes, this funky issue was apparently just a Chrome cache problem. Cleared cache and the problem disappeared.