@Gargron No, I'm running Firefox 72, and now I'm seeing the problem again.