Hi Elihu,
This is a known issue that was introduced in Chrome 86.
Dev teams are currently working on addressing this.
Seems that the only recourse at this time is to use a different browser.
//Henk
------------------------------
HENK CAZEMIER
------------------------------