I just upgraded to Chrome 77.0.3865.90 from whatever minor version of v77 I was on when I upgraded from v76 and the problem seems to have gone away. It was probably a browser bug in the initial v77 release (it also broke WordPress).
1 Like