@Gargron @chad You know what? I think I just found a bug -- because it's re-appeared after I looked in another web browser.