The work-around I noted above fixed the issue for me, so I’m no longer able to reproduce it. I was using Chrome Version 88.0.4324.96 (Mac OS).
The work-around I noted above fixed the issue for me, so I’m no longer able to reproduce it. I was using Chrome Version 88.0.4324.96 (Mac OS).