@dnzrzx34
It seems that Chrome Developer/Canary version 117 has partly/mostly resolved the issue, but not completely.